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 "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2018/11/29 20:27:00 UTC

[jira] [Assigned] (OAK-7926) ACLs for the mounted principal should use the mounted permission store

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

Tomek Rękawek reassigned OAK-7926:
----------------------------------

    Assignee: Tomek Rękawek

> ACLs for the mounted principal should use the mounted permission store
> ----------------------------------------------------------------------
>
>                 Key: OAK-7926
>                 URL: https://issues.apache.org/jira/browse/OAK-7926
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: security
>            Reporter: Tomek Rękawek
>            Assignee: Tomek Rękawek
>            Priority: Major
>             Fix For: 1.10
>
>
> Right now, the permission store is aware of the mounts configured with the {{MountInfoProvider}}: adding a ACL for the content stored in a mount will result in creating the {{rep:Permissions}} in {{/jcr:system/rep:permissionStore/oak:mount-MOUNT-WORKSPACE}} permission store. This path should be mounted as well. This way the content and its permissions can be mounted together. See OAK-3777 for more details on this.
> As in OAK-7725, it's also possible to include a {{rep:AuthorizableFolder}} in a mount. This way, the users created in such folder will be stored in the mounted repository (when using Composite Node Store). Permissions for such users should be also stored in the mounted permission store, rather than general one.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)