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 2022/01/04 19:42:00 UTC

[jira] [Resolved] (SLING-11023) Support setting jcr:mixinTypes and jcr:primaryType for nested authorizable properties

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

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

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

> Support setting jcr:mixinTypes and jcr:primaryType for nested authorizable properties
> -------------------------------------------------------------------------------------
>
>                 Key: SLING-11023
>                 URL: https://issues.apache.org/jira/browse/SLING-11023
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Eric Norman
>            Assignee: Eric Norman
>            Priority: Major
>             Fix For: JCR Jackrabbit User Manager 2.2.18
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> When creating or updating a user/group it may be necessary to supply the jcr:primaryType and/or jcr:mixinTypes values for one or more of the container nodes to satisfy constraints.
> For example:
> {code:java}
> curl -Fprivate/jcr:mixinTypes=mymix:samplemix  \
>      -Fprivate2/jcr:primaryType=my:sample  \
>      http://localhost:8080/people/user/testuser1.update.html{code}



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