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 2014/09/25 15:26:33 UTC

[jira] [Updated] (OAK-1653) [User Management] Make rep:userManagement an aggregate

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

angela updated OAK-1653:
------------------------
    Issue Type: Wish  (was: Improvement)

> [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: security
>            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)