jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-1653) [User Management] Make rep:userManagement an aggregate
Date Tue, 01 Apr 2014 09:48:18 GMT

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

angela updated OAK-1653:
------------------------

    Summary: [User Management] Make rep:userManagement an aggregate  (was: [User Management]
Make rep:userManagement an aggregate of 'member management' and 'rest of user management')

> [User Management] Make rep:userManagement an aggregate
> ------------------------------------------------------
>
>                 Key: OAK-1653
>                 URL: https://issues.apache.org/jira/browse/OAK-1653
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>            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.2#6252)

Mime
View raw message