[wsas-java-dev] [jira] Resolved: (WSAS-190) rahas module getting disengaged from the service when a securiy scenario is applied

[Afkham Azeez (JIRA)]

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

Afkham Azeez resolved WSAS-190.
-------------------------------

    Resolution: Not a bug

The Rampart & Rahas modules work together. Each security scenario describes which modules(Rampart only or Rampart + Rahas). 

So, if you apply a scenario that requires Rampart only, Rahas will be disengaged for obvious reasons. The reason behind having easily selectablesecurity scenarios is that the user does not have to worry about security policies or the required modules.

Also, simply engaging Rahas, will not do anything useful for the end user. 

> rahas module getting disengaged from the service when a securiy scenario is applied
> -----------------------------------------------------------------------------------
>
>                 Key: WSAS-190
>                 URL: http://www.wso2.org/jira/browse/WSAS-190
>             Project: WSO2 WSAS-Java
>          Issue Type: Bug
>          Components: MgtConsole-UI
>         Environment: Windows XP, JDK 1.4.2_13,  Firefox version 1.5.0.8
>            Reporter: Evanthika Amarasiri
>         Assigned To: Afkham Azeez
>
> Below are the steps taken to reproduce the error
> 1. Select a service 
> E.g.:- echo
> 2. Engage the module rahas1.1 to the service. (It would engaged the rampart1.1 module as well)
> 3. Through "Services > echo > Security Configuration" apply a security scenario to the echo service
> 4. Go to "Services > echo > Engage Modules" to see the module which have been engaged to the service. You will notice that the rahas1.1 module has been disengaged from 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