You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Eric Norman (JIRA)" <ji...@apache.org> on 2010/03/25 19:42:27 UTC
[jira] Resolved: (SLING-1458) The jackrabbit.accessmanager bundle
needs to provide a mechanism to re-order the ACEs in the ACL
[ https://issues.apache.org/jira/browse/SLING-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Norman resolved SLING-1458.
--------------------------------
Resolution: Fixed
Fix Version/s: JCR Base 2.1.0
JCR ContentLoader 2.0.8
Launchpad Testing 6
fix committed in r927532
> The jackrabbit.accessmanager bundle needs to provide a mechanism to re-order the ACEs in the ACL
> ------------------------------------------------------------------------------------------------
>
> Key: SLING-1458
> URL: https://issues.apache.org/jira/browse/SLING-1458
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Jackrabbit Access Manager 2.0.6
> Reporter: Eric Norman
> Assignee: Eric Norman
> Fix For: Launchpad Testing 6, JCR ContentLoader 2.0.8, JCR Jackrabbit Access Manager 2.0.6, JCR Base 2.1.0
>
>
> As described by Ray Davis on the jackrabbit-users mailing list (see http://www.mail-archive.com/users@jackrabbit.apache.org/msg14734.html ), the order of the ACEs in the AccessControlList is important for resolving conflicting group permissions. When resolving the permissions, if the current user is a member of multiple groups that have permissions specified, then the last group in the ACL wins if there are any conflicts.
> The jackrabbit.accessmanager bundle must provide a RESTful mechanism to re-order the existing ACEs in the ACL.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.