[
https://jira.jboss.org/jira/browse/JBSEAM-3664?page=com.atlassian.jira.pl...
]
Shane Bryzak closed JBSEAM-3664.
--------------------------------
Resolution: Done
PermissionMapper will now raise the org.jboss.seam.security.defaultResolverChainCreated
event when the default resolver chain is created, allowing it to be modified or
re-ordered.
change the priority of PermissionResolvers
------------------------------------------
Key: JBSEAM-3664
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3664
Project: Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.1.0.GA
Reporter: Marco R�¶�¶sli
Assignee: Shane Bryzak
Fix For: 2.1.2.CR1
If the Jpa Permission Store is used and a rule-based-permission-resolver and a
persistent-permission-resolver is configured, the order for looking up permissions is:
1) DroolsFile, 2)persistent-permission-resolver 3) Other permission-resolvers what
implments the permission-resolver interface
It would be nice if it's possible to change the order for looking up the permissions
--
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