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/11/10 15:37:58 UTC
[jira] [Resolved] (OAK-3627) Allow to set ACLs on not-yet existing
nodes
[ https://issues.apache.org/jira/browse/OAK-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela resolved OAK-3627.
-------------------------
Resolution: Later
resolving issue. this could be implemented using a custom authorization model (as it actually used to be in jackrabbit 2.x)
> 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
>
> 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
(v6.3.4#6332)