[ http://wso2.org/jira/browse/WSAS-618?page=all ]
Nandana Mihindukulasooriya updated WSAS-618:
--------------------------------------------
Attachment: WSAS-618.patch
custom_policies_edit.xsl
security_configuration_options.xsl
Custom policy editor should be able to
1. create a custom security according to user input
2. apply it to a specific service
3. persist the custom policy and make it appear in the default security
configuration
Step 1 will have to be done completely in the front end and will be a
configuration wizard like the data services UI.
Step 2 can already done using the Service Admin.
Step 3, method is added to SecurityScenarioConfigAdmin to persist the custom
security policy under /conf/rampart so that it can be reused and can be found
in security configuration. This saves the custom policy file in conf/rampart
and adds the scenario to the database. At the moment, scenario-config.xml is
not altered.
> Add a custom policy editor to WSAS security configuration
> ----------------------------------------------------------
>
> Key: WSAS-618
> URL: http://wso2.org/jira/browse/WSAS-618
> Project: WSO2 WSAS
> Issue Type: New Feature
> Components: MgtConsole-UI
> Reporter: Nandana Mihindukulasooriya
> Assigned To: Nandana Mihindukulasooriya
> Priority: Critical
> Fix For: 2.2
>
> Attachments: custom_policies_edit.xsl,
> security_configuration_options.xsl, WSAS-618.patch
>
>
> Add a custom policy editor to WSAS security configuration, so users can
> either use existing security policies or create new security policies to to
> match the exact requirement.
--
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
