You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2015/02/16 17:19:12 UTC
[jira] [Commented] (OAK-1653) [User Management] Make
rep:userManagement an aggregate
[ https://issues.apache.org/jira/browse/OAK-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322938#comment-14322938 ]
angela commented on OAK-1653:
-----------------------------
Resolving later as this isn't planned for the near future. As workaround the same effect can also be achieved by creating access control entries with restrictions.
> [User Management] Make rep:userManagement an aggregate
> ------------------------------------------------------
>
> Key: OAK-1653
> URL: https://issues.apache.org/jira/browse/OAK-1653
> Project: Jackrabbit Oak
> Issue Type: Wish
> Components: core
> Reporter: Vikas Saurabh
> Assignee: angela
> Priority: Minor
>
> Following up disussion on [oak dev list | https://mail-archives.apache.org/mod_mbox/jackrabbit-oak-dev/201404.mbox/%3CCF6047EA.194BC%25anchela%40adobe.com%3E].
> A common use-case for user management is to have member management but not other permissions. Currently, rep:userManagement is a all or nothing privilege.
> It would useful to split this into something which targets membership management and other stuff (I don't know other detail of user-management... we might want more fragments here)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)