[
https://issues.apache.org/jira/browse/JCR-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-650.
-------------------------------
Resolution: Fixed
Committed the contributed access manager in revision 526687.
I modified the class somewhat, backporting it to Java 1.4 and streamlining some
of the logic, but made no functional changes. Note that the fully qualified
name of the class is now
org.apache.jackrabbit.core.security.SimpleJBossAccessManager (no .jboss
package, and JBoss with a capital B).
It seems that the only JBoss-specific part of the class is the use of the
"Roles" principal group. How about generalizing the class so that it uses all
the principals associated with the subject and not just the "Roles" principals?
I think it would also make sense to use the standard JAAS Permission model
instead of the custom rolemapping.properties file for access control.
Thanks for the contribution!
> SimpleJbossAccessManager
> ------------------------
>
> Key: JCR-650
> URL: https://issues.apache.org/jira/browse/JCR-650
> Project: Jackrabbit
> Issue Type: New Feature
> Components: security
> Environment: Jboss 4.0.5.GA (should work on most any), Jackrabbit
> 1.1, either JCA or server .WAR deployment
> Reporter: Darren Hartford
> Assigned To: Jukka Zitting
> Fix For: 1.3
>
> Attachments: pom.xml, SimpleJbossAccessManager.java
>
>
> http://wiki.apache.org/jackrabbit/SimpleJbossAccessManager
> Code contribution
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
