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 2017/07/19 07:47:00 UTC

[jira] [Commented] (OAK-6469) CompositePermissionProvider should implement AggregatedPermissionProvider

    [ https://issues.apache.org/jira/browse/OAK-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092729#comment-16092729 ] 

angela commented on OAK-6469:
-----------------------------

[~stillalex], there was a reason for not making the {{CompositePermissionProvider}} an {{AggregatedPermissionProvider}}, but i don't recall it right now... will take a look at the patch asap maybe i remember it.

> CompositePermissionProvider should implement AggregatedPermissionProvider
> -------------------------------------------------------------------------
>
>                 Key: OAK-6469
>                 URL: https://issues.apache.org/jira/browse/OAK-6469
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, security
>            Reporter: Alex Deparvu
>            Assignee: Alex Deparvu
>         Attachments: OAK-6469.patch
>
>
> A more in-depth followup of OAK-6451. It turns out you can't mix CUG setup with the Multiplexing setup because the {{CompositePermissionProvider}} cannot contain another composite.
> Making {{CompositePermissionProvider}} implement {{AggregatedPermissionProvider}} opens the door for composites of composites.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)