[wsas-java-dev] [jira] Resolved: (WSAS-335) Rampart/rahas modules are not disengaged automatically when security is disabled

[Afkham Azeez (JIRA)]

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

Afkham Azeez resolved WSAS-335.
-------------------------------

    Fix Version/s: Nightly
       Resolution: Fixed

Fixed

> Rampart/rahas modules are not disengaged automatically when security is disabled
> --------------------------------------------------------------------------------
>
>                 Key: WSAS-335
>                 URL: http://www.wso2.org/jira/browse/WSAS-335
>             Project: WSO2 WSAS
>          Issue Type: Bug
>    Affects Versions: Nightly
>         Environment: winxp, jdk15
>            Reporter: Charitha Kankanamge
>         Assigned To: Afkham Azeez
>            Priority: Critical
>             Fix For: Nightly
>
>
> This is clearly a regression bug. When disabling security of a service,  rampart/rahs modules are not disengaged automatically.
> Steps to reproduce:
> ===============
> 1. Select a service and assign security scenario 2 (Sign only)
> 2.Click on 'Manage Module Engagements' link of that service.
>     Rampart will be listed as engaged module
> 3. Now disable security of that service by selecting 'Unsecured' option
> 4. Click on 'Manage Module Engagements' link again
> Rampart is still engaged to the service.

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