[wsas-java-dev] [jira] Updated: (WSAS-662) An additional policy is applied when creating a service archive using an existing service

[Afkham Azeez (JIRA)]

     [ http://wso2.org/jira/browse/WSAS-662?page=all ]

Afkham Azeez updated WSAS-662:
------------------------------


Here is how we can fix this:

Introduce a special parameter, "WSASRampartConfig", which will have the scenario ID, keystore/user/role information. 
In the DeploymentInterceptor, we can look for this parameter, and if it is available, we will set the proper stuff in the DB.

> An additional policy is applied when creating a service archive using an existing service 
> ------------------------------------------------------------------------------------------
>
>                 Key: WSAS-662
>                 URL: http://wso2.org/jira/browse/WSAS-662
>             Project: WSO2 WSAS
>          Issue Type: Bug
>          Components: core
>    Affects Versions: Nightly
>         Environment: winxp, jdk15, WSAS-2.2-qabuild2, firefox2.0.0.9
>            Reporter: Charitha Kankanamge
>         Assigned To: Saminda Wishwajith Abeyruwan 
>            Priority: Critical
>
> 1. Assign 'Sign only' security scenario to an existing service
> 2. Now select the service group and click on 'Create service archive'
> 3. Undeploy the original service and restart WSAS
> 4. Deploy the generated service archive
> 5. Go to 'Services and service group management' page and click 'policy' link of the service
> You will get two policies. One is the expected 'SigOnly' policy. The additional policy is a UT policy which has not been specified by user.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira