Uploaded image for project: 'Jackrabbit Content Repository'
  1. Jackrabbit Content Repository
  2. JCR-650

SimpleJbossAccessManager

        Details

        • Type: New Feature
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Affects Version/s: None
        • Fix Version/s: 1.3
        • Component/s: security
        • Labels:
          None
        • Environment:
          Jboss 4.0.5.GA (should work on most any), Jackrabbit 1.1, either JCA or server .WAR deployment
        1. XML File
          pom.xml
          1 kB
          Darren Hartford
        2. Java Source File
          SimpleJbossAccessManager.java
          6 kB
          Darren Hartford

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          jukkaz Jukka Zitting added a comment -

          Looks good! I'll see if I can include this already in the 1.3 release.

          Show
          jukkaz Jukka Zitting added a comment - Looks good! I'll see if I can include this already in the 1.3 release.
          Hide
          Permalink
          jukkaz Jukka Zitting added a comment -

          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!

          Show
          jukkaz Jukka Zitting added a comment - 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!

            People

            • Assignee:
              jukkaz Jukka Zitting
              Reporter:
              dhartford Darren Hartford
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development