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

Charitha Kankanamge (JIRA) jira at wso2.org
Wed Nov 14 23:21:14 PST 2007


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

Charitha Kankanamge reopened WSAS-263:
--------------------------------------

             
This is not fixed yet. Checked in WSAS-2.1.

> Set the security configuration in WSAS management console when it is given in the services.xml
> ----------------------------------------------------------------------------------------------
>
>                 Key: WSAS-263
>                 URL: http://www.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://www.wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        




More information about the Wsas-java-dev mailing list