[SLING-1016] Make membership management depend on the principal name not the URI of the principal, since the principal name is already unique.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: JCR Jackrabbit User Manager 2.0.4
• Component/s: JCR
• Assignee: Unassigned
• Reporter: Ian Boston
• Created: 22/Jun/09 10:24
• Updated: 14/Jul/09 16:31
• Resolved: 14/Jul/09 16:31

Description

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 <[e-mail]> wrote:

I was wondering,

curl -F:member=/system/userManager/user/ieb http://admin:admin@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:admin@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:admin@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

----------------------------------