[
https://issues.apache.org/jira/browse/JCR-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14041886#comment-14041886
]
angela commented on JCR-3778:
-----------------------------
did you mean new privileges?
- rep:writeMemberIDs is already covered by rep:userManagement privilege (see
also OAK-1653 for making this an aggregate), but only in Oak and i not sure
it's feasible to port that back to jackrabbit... so, you won't be able to make
use of it in our products as long as they have to support both repositories.
- not sure about rep:readMemberIDs. currently all protected items (except for
access control content) is controlled by regular read permission.
regarding
{quote}
Maybe it would be better to always return an Authorizable for the "member"
related methods
{quote}
maybe... but it's still sort of 'implementation dependent'...
the current situation is for sure the most restrictive one and only exposes
information that is guaranteed to be accessible to the editing session.
> getMemberIDs() method for Group
> -------------------------------
>
> Key: JCR-3778
> URL: https://issues.apache.org/jira/browse/JCR-3778
> Project: Jackrabbit Content Repository
> Issue Type: Wish
> Components: jackrabbit-api
> Affects Versions: 2.7.5
> Reporter: Lars Krapf
> Assignee: angela
> Priority: Minor
>
> Provide a method to get a list of all memberIDs (strings) from a group, given
> that a user has read access to that group.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
