[jira] [Commented] (OAK-3627) Allow to set ACLs on not-yet existing nodes

["angela (JIRA)" <ji...@apache.org>]

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

angela commented on OAK-3627:
-----------------------------

[~kwin], just for the record: the new authorization model introduced with OAK-8190 would allow for defining entries for non-existing nodes. while the original purpose of OAK-8190 was limited to system users, the model is designed such that it can be extended and used for any type of principal... as long as the configured filterprovider is able to handle it... but the code makes no assumption otherwise wrt the type of principal and if/how they are represented in the repository. in other words: the filter implementation defines if a given (set of) principals is supported and where to store the policy associated with a given principal.

> Allow to set ACLs on not-yet existing nodes
> -------------------------------------------
>
>                 Key: OAK-3627
>                 URL: https://issues.apache.org/jira/browse/OAK-3627
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: core
>            Reporter: Konrad Windszus
>            Priority: Major
>
> With Jackrabbit 2 it was possible to set ACLs for nodes which do not exist yet through Principal-based ACLs (http://wiki.apache.org/jackrabbit/AccessControl#Principal-based_ACLs).
> With Oak this is no longer possible as the principal based ACEs are not supported (https://jackrabbit.apache.org/oak/docs/security/accesscontrol/differences.html). Since there are valid use cases for setting ACEs prior to creating the according nodes it would be good, if Oak would support this as well.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)