[
http://jira.jboss.com/jira/browse/SECURITY-259?page=all ]
Stefan Guilhen closed SECURITY-259.
-----------------------------------
Resolution: Done
- Application policies specified through the microcontainer now can include an <acl>
section to specify the acl-modules that are to be used. The
ApplicationPolicyMetaDataFactory has been updated to parse the ACL configuration and
create an ACLPolicyBean. This bean generated the ACLInfo that is included in the
ApplicationPolicy object that is created.
- Included a new test case (ACLPolicyTestCase) to demonstrate the configuration of
acl-modules in an application-policy.
- The headers of the source files have been updated to fix the year value (2006 to 2008).
- AuthenticationInfo and JASPIAuthenticationInfo now override the create method so that
the merged info object has the same type of the info where merge is being called.
Add ACL configuration to the ApplicationPolicyMetaDataFactory
-------------------------------------------------------------
Key: SECURITY-259
URL:
http://jira.jboss.com/jira/browse/SECURITY-259
Project: JBoss Security and Identity Management
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Affects Versions: 2.0.2.CR6
Reporter: Stefan Guilhen
Assigned To: Stefan Guilhen
Fix For: 2.0.2.GA
The ApplicationPolicyMetaDataFactory must be able to create application policies that
contain an ACL configuration. The ACL providers must be specified through the <acl>
element:
<application-policy xmlns="urn:jboss:security-beans:1.0"
name="policy">
<authentication>
....
</authentication>
<acl>
<acl-module code="org.jboss.security.acl.ACLProviderImpl"
flag="required">
<module-option name="option">value</module-option>
</acl-module>
</acl>
...
</application-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