[
https://issues.apache.org/jira/browse/OAK-8023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761662#comment-16761662
]
angela commented on OAK-8023:
-----------------------------
[~stillalex], having thought about it again, i found an alternative approach
that would not require to introduce an odd marker-path: if we the rep:nodePath
restriction is defined to be of type STRING no conversion will be made and
empty string would still work. The downside was that the conversion from jcr to
oak path (and vice versa) is no longer performed. so, usage of expanded names
and namespace re-mappings would no longer work.
> AccessControlManagerImpl can not handle repository level when editing
> policies by principal
> -------------------------------------------------------------------------------------------
>
> Key: OAK-8023
> URL: https://issues.apache.org/jira/browse/OAK-8023
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, security
> Reporter: angela
> Assignee: angela
> Priority: Minor
> Fix For: 1.12, 1.11.0
>
> Attachments: OAK-8023-2.patch, OAK-8023.patch
>
>
> [~stillalex], it seems that editing access control by principal in the
> default implementation doesn't allow for applying entries to the 'null' path.
> initially i thought that we can use an empty string value instead for the
> {{rep:nodePath}}, but that doesn't work as it gets converted to "." for some
> reason.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
