[
https://issues.apache.org/jira/browse/OAK-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629116#comment-13629116
]
angela commented on OAK-707:
----------------------------
simplified AccessControlConfiguration#getAccessControlManager as the permission
provider
can now be created on demand in the ac manager.
> Review interaction between AccessControlManager and PermissionManager
> ---------------------------------------------------------------------
>
> Key: OAK-707
> URL: https://issues.apache.org/jira/browse/OAK-707
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: core, jcr
> Reporter: angela
> Priority: Minor
>
> the following methods on the access control manager interface require
> interaction with the permission evaluation:
> #hasPrivileges(String, Privilege[])
> #getPrivileges(String)
> #hasPrivileges(String, Set<Principal>, Privilege[])
> #getPrivileges(String, Set<Principal>)
> right now those methods are not supported if there was no permission provider
> passed to the acmgr constructor, which obviously is far from being optimal.
> in general i see the need for closer interaction between oak-api and the
> permission evaluation... (see also the related TODO with
> Root#getCommitSubject)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
