[ http://wso2.org/jira/browse/WSAS-662?page=comments#action_14322 ] Charitha Kankanamge commented on WSAS-662: ------------------------------------------
It has been noticed that the additional policy is taken from the database of the WSAS instance. So the functionality may not be affected if the created service archive is deployed in the same WSAS instance. However, the generated service archive will give more problems if it is deployed in a new WSAS instance. Hence, when creating a service archive from a service which is configured with sec-scenarios, the generated archive should contain all the meta-data related to the rampart configuration. > 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: Afkham Azeez > 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 _______________________________________________ Wsas-java-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
