[jira] [Resolved] (SLING-11034) Allow option to expose nested authorizable properties as child resources

["Eric Norman (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-11034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Norman resolved SLING-11034.
---------------------------------
    Resolution: Fixed

merged PR at:  [{{62d5643}}|https://github.com/apache/sling-org-apache-sling-jcr-jackrabbit-usermanager/commit/62d5643c901a213c9c0c80ca8555f3b2514efd71]

> Allow option to expose nested authorizable properties as child resources
> ------------------------------------------------------------------------
>
>                 Key: SLING-11034
>                 URL: https://issues.apache.org/jira/browse/SLING-11034
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Eric Norman
>            Assignee: Eric Norman
>            Priority: Major
>             Fix For: JCR Jackrabbit User Manager 2.2.18
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> When nested properties are set on a user or group, it is not convenient to read those property values from the AuthorizableResource without writing extra code.
> Expected:
> For any nested authorizable properties, provide a NestedAuthorizableResource child resource for each of the property containers.
> For example to get a user with it's direct children:
> {code:java}
> $ curl http://localhost:8080/system/userManager/user/myuser.tidy.1.json{code}
> Or to access the a "private" nested properties child directly:
> {code:java}
> $ curl http://localhost:8080/system/userManager/user/myuser/private.tidy.json{code}
>  
> This capability should be able to be turned on or off via configuration.  Probably off by default for backward compatibility.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)