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 2016/03/03 18:04:18 UTC

[jira] [Commented] (OAK-3777) Multiplexing support in default PermissionStore implementation

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

angela commented on OAK-3777:
-----------------------------

quoting from parent issue:
{quote}
as already stated in the discussion during the last Oakathon the whole security
part in oak is pluggable at runtime and any module may define with it's own
{{RepositoryInitializer}}, {{Validator}} and {{CommitHook}} implementations. My
gut feeling therefore is that we shall not twist the current default
implementations to somehow get it work with this approach but rather make sure
all multiplexing parts are treated like a separate repo with their own
configuration(s). Also we must not assume that custom implementations are free
of 'global' information... so, ultimately I have the feeling that using the
composite security setup parts might be better suited for this than bending the
existing code to respect the multiplexing.
{quote}

> Multiplexing support in default PermissionStore implementation
> --------------------------------------------------------------
>
>                 Key: OAK-3777
>                 URL: https://issues.apache.org/jira/browse/OAK-3777
>             Project: Jackrabbit Oak
>          Issue Type: Technical task
>          Components: core
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>
> Similar to other parts we need to prototype support for multiplexing in default permission store



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)