[
https://issues.apache.org/jira/browse/SLING-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887695#comment-13887695
]
Amit Gupta commented on SLING-3361:
-----------------------------------
only fixed the issue in
Node createPath(String path,
String intermediateNodeType,
String nodeType,
Session session,
boolean autoSave)
for the other variant, I am not sure if we need to fix that as well. As caller
is already passing parentNode, so we can assume that user already have access
to parentNode.
> JcrResourceUtil.createPath does not work in certain ACL setups
> --------------------------------------------------------------
>
> Key: SLING-3361
> URL: https://issues.apache.org/jira/browse/SLING-3361
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Resource 2.3.0
> Reporter: Amit Gupta
> Assignee: Amit Gupta
> Priority: Minor
> Fix For: JCR Resource 2.3.2
>
> Attachments: bug.patch
>
>
> JcrResourceUtil.createPath fails for path such as
> /a/b/c/d/e
> where /ab/c already exists and d/e needs to be created in certain acl setups
> i.e.
> user has read & write permission to /a/b/c not don't have read permission on
> /.
> Current implementation expects that user would have read permission on root
> node.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
