[
https://jira.jboss.org/jira/browse/SECURITY-288?page=com.atlassian.jira.p...
]
Anil Saldhana commented on SECURITY-288:
----------------------------------------
SECURITY-287 added a method called as "supports". This will help in the
flexibility of the mapping framework.
We will continue to support the explicit <role-mapping> element in a deprecated
manner.
SecurityContext.getMappingManager gets us the mapping manager from where we can map.
Mapping Flexibility needed in the 5.0 schema
--------------------------------------------
Key: SECURITY-288
URL:
https://jira.jboss.org/jira/browse/SECURITY-288
Project: JBoss Security and Identity Management
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Identity, JBossSX
Affects Versions: 2.0.2.CR7
Reporter: Anil Saldhana
Assignee: Stefan Guilhen
Fix For: 2.0.2.CR8
We need some mapping schema flexibility. My earlier attempt of directly doing a
role-mapping element needs to be deprecated and we need something like the following:
<application-policy name="test">
<authentication/>
<authorization/>
<mapping>
<type="principal">
<mapping-module>....</mapping-module>
</type>
<type="identity">
<mapping-module>....</mapping-module>
</type>
<type="rolemapping">
<mapping-module>....</mapping-module>
</type>
</mapping>
</application-policy>
the element names in type (principal, identity, rolemapping) should just be arbitrary
strings. Users should be able to add anything of their own.
getMappingInfo(String mappingType) should return the MappingInfo.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira