sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konrad Windszus (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SLING-6753) User Manager: Expose user's path as property
Date Thu, 30 Mar 2017 11:19:41 GMT
Konrad Windszus created SLING-6753:
--------------------------------------

             Summary: User Manager: Expose user's path as property
                 Key: SLING-6753
                 URL: https://issues.apache.org/jira/browse/SLING-6753
             Project: Sling
          Issue Type: Improvement
          Components: JCR
            Reporter: Konrad Windszus
            Assignee: Konrad Windszus
             Fix For: JCR Jackrabbit User Manager 2.2.6


With the support of nested user properties (SLING-6747) the resource provider will still only
expose direct user properties through its {{ValueMap}}. This is a limitation of the Jackrabbit
Security API and its `getPropertyNames()` method (https://jackrabbit.apache.org/api/2.8/org/apache/jackrabbit/api/security/user/Authorizable.html#getPropertyNames()).
To make it possible to read nested user properties through some other means, it would be helpful
to retrieve the underlying user path through the `AuthorizableValueMap`, to then be able to
access the nested properties via regular means (i.e. Sling Resource API or JCR API).

This is especially important since in Oak the user path is no longer predictable (http://jackrabbit.apache.org/oak/docs/security/user/authorizablenodename.html).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message