[
https://issues.apache.org/jira/browse/SLING-7886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-7886.
--------------------------------
Resolution: Fixed
Fixed at:
[https://github.com/apache/sling-org-apache-sling-jcr-jackrabbit-usermanager/commit/d89bcd92f48bf42c28e9cd37a81d8f5b38361db5#diff-ad9077962ed0c1d4663683f490b1a073]
[https://github.com/apache/sling-org-apache-sling-jcr-jackrabbit-usermanager/commit/141637a6afaae62f593eb45ab4721b5b356e3182#diff-ad9077962ed0c1d4663683f490b1a073]
Tests added at:
[https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/commit/a65f6db6734fc04f288e307fc94c863ca1e69ee1]
> AuthorizablePrivilegesInfo returns incorrect information for non-admin user
> who has been granted sufficient privileges to do User/Group Management
> activites
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-7886
> URL: https://issues.apache.org/jira/browse/SLING-7886
> Project: Sling
> Issue Type: Bug
> Affects Versions: JCR Jackrabbit User Manager 2.2.6
> Reporter: Eric Norman
> Assignee: Eric Norman
> Priority: Major
> Fix For: JCR Jackrabbit User Manager 2.2.8
>
>
> AuthorizablePrivilegesInfo returns incorrect information for non-admin user
> who has been granted sufficient privileges to do User/Group Management
> activities
> It looks like the oak impl of UserManager requires these privileges to be
> granted on the /home/users or /home/groups folders for the user to be able to
> do user/group management calls:
> jcr:readAccessControl
> jcr:modifyAccessControl
> rep:userManagement
> jcr:read
> rep:write
>
> So if those privileges are granted, then the AuthorizablePrivilegesInfo#can*
> calls should return true.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
