[
http://jira.jboss.com/jira/browse/SECURITY-260?page=all ]
Stefan Guilhen closed SECURITY-260.
-----------------------------------
Resolution: Done
The security-config schemas have been moved from metadata to jbosssx. The classes involved
in parsing application policies have been updated to allow the specification of acl
configurations and tests have been expanded to guarantee that the expected ACLInfo objects
are created and set into the ApplicationPolicy.
Allow the declaration of ACLconfigurations in application policies
specified in static XML files.
-------------------------------------------------------------------------------------------------
Key: SECURITY-260
URL:
http://jira.jboss.com/jira/browse/SECURITY-260
Project: JBoss Security and Identity Management
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: AS-Integration
Affects Versions: 2.0.2.CR6
Reporter: Stefan Guilhen
Assigned To: Stefan Guilhen
Fix For: 2.0.2.GA
Application policies can be declared in static XML files (e.g. login-config.xml) that are
parsed by the security framework. We need to support the specification of ACL providers as
part of an application policy, like the example bellow:
<policy>
<application-policy name="policy>
<authentication>
...
</authentication>
<acl>
<acl-module code="org.jboss.security.acl.ACLProviderImpl"
flag="required">
<module-option
name="persistenceStrategy">org.jboss.security.acl.JPAPersistenceStrategy</module-option>
</acl-module>
</acl>
...
</application-policy>
</policy>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira