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 Schreiber (Jira)" <ji...@apache.org> on 2020/10/16 12:45:00 UTC
[jira] [Comment Edited] (OAK-9183) verify 'Mapping API Calls to
Privileges' wrt to move operations
[ https://issues.apache.org/jira/browse/OAK-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215377#comment-17215377 ]
Angela Schreiber edited comment on OAK-9183 at 10/16/20, 12:44 PM:
-------------------------------------------------------------------
Committed revision 1882583: fixed documentation and added 2 more test cases used to verify it.
was (Author: anchela):
Committed revision 1882583.
> verify 'Mapping API Calls to Privileges' wrt to move operations
> ---------------------------------------------------------------
>
> Key: OAK-9183
> URL: https://issues.apache.org/jira/browse/OAK-9183
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: doc
> Reporter: Angela Schreiber
> Assignee: Angela Schreiber
> Priority: Minor
> Fix For: 1.36.0
>
>
> [~fmeschbe], as discussed today, i suspect that the section about moving nodes (see http://jackrabbit.apache.org/oak/docs/security/privilege/mappingtoprivileges.html#Move_and_Import) doesn't not list the complete set of privileges required for a move operation, namely the ability to remove the source node itself (not just disconnect it from the parent).
> i will verify that again and if true adjust the documentation (both for session and workspace move).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)