[wsas-java-dev] [jira] Resolved: (WSAS-263) Set the security configuration in WSAS management console when it is given in the services.xml

[Afkham Azeez (JIRA)]

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

Afkham Azeez resolved WSAS-263.
-------------------------------

    Resolution: Won't Fix

The sec policy in the services.xml do not include the Rampart configuration policies. Hence we cannot properly figure out the users/roles/keystore info related to a sec scenario. Hence this will have to be configured using the console

> Set the security configuration in WSAS management console when it is given in the services.xml
> ----------------------------------------------------------------------------------------------
>
>                 Key: WSAS-263
>                 URL: http://wso2.org/jira/browse/WSAS-263
>             Project: WSO2 WSAS
>          Issue Type: Bug
>    Affects Versions: Nightly
>         Environment: winxp, jdk15
>            Reporter: Charitha Kankanamge
>         Assigned To: Afkham Azeez
>
> When user defines the service policy in services.xml, it does not affect the security configuration settings in wsas management console. Service policy is updated correctly. However security configuration is changed to the default 'Unsecured' option. This can be identified clearly when creating a service archive using a service which is engaged with a security scenario.
> Steps to reproduce:
> ================
> 1. Deploy a service 
> 2. Configure a security scenario (eg:- UT over https)
> 3. Create a service archive from that service (Services > [servicename] Service Group-->Create service archive)
> 4. Remove the existing service and deploy the new one
> 5. Navigate to 'Security Configuration' page
> 'Unsecured' option is selected

-- 
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