[
https://issues.apache.org/jira/browse/OAK-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418117#comment-13418117
]
angela commented on OAK-64:
---------------------------
one more thing that isn't documented with your half way fix: the jcr:all
privilege must
include all privileges (including custom)... that requirement of the spec is
violated
right now and there is not TODO for that since it was obvious IMO.
and a final question: what does the client (i assume it's CQ) do with a custom
privilege
if access control is not implemented altogether? i would suggest that the
client should
deal with failing privilege registration instead of adding hacks to oak.
> Privilege Management
> --------------------
>
> Key: OAK-64
> URL: https://issues.apache.org/jira/browse/OAK-64
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: core, jcr
> Reporter: angela
> Assignee: angela
>
> implement privilege management such as defined by jackrabbit API
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
