[
https://issues.apache.org/jira/browse/SLING-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan Jose Vazquez Delgado updated SLING-1016:
---------------------------------------------
Affects Version/s: (was: JCR Jackrabbit User Manager 2.0.4)
Remaining Estimate: 0h
Original Estimate: 0h
Patch applied in rev. 787207. Thank Ian for providing this patch. Please check
and close if this works for you.
> Make membership management depend on the principal name not the URI of the
> principal, since the principal name is already unique.
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-1016
> URL: https://issues.apache.org/jira/browse/SLING-1016
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Reporter: Ian Boston
> Attachments: SLING-1016.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> As per thread on sling-dev
> -----------------------
> You are probably right, the principal name is sufficient to find the
> authorizable. Can you make the patch?
> Thanks!
> On Fri, Jun 19, 2009 at 7:43 AM, Ian Boston <i...@tfd.co.uk> wrote:
> I was wondering,
> curl -F:member=/system/userManager/user/ieb http://admin:ad...@localhost
> :8080/system/userManager/group/g-group1.update.json
> appears to be the way to add members to groups
> or
> curl -F:member=../../ieb http://admin:ad...@localhost
> :8080/system/userManager/group/g-group1.update.json
> I can see where this is in the code, but it looks a bit odd and slightly
> hard for a UI developer to work with when
> curl -F:member=ieb http://admin:ad...@localhost
> :8080/system/userManager/group/g-group1.update.json
> would have worked. Was there a reason I am missing this is like it is ?
> I would like to change it, happy to do a patch.
> Ian
> ----------------------------------
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
