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 2013/04/22 14:09:16 UTC
[jira] [Comment Edited] (OAK-787) Accessibility of NodeTypes,
Namespaces and Privileges
[ https://issues.apache.org/jira/browse/OAK-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637947#comment-13637947 ]
angela edited comment on OAK-787 at 4/22/13 12:08 PM:
------------------------------------------------------
patch 1:
define built-in default policy that grants
read access for node types, namespace and privileges and adjust permission evaluation accordingly (note: isGranted is not yet adjusted, policy can in this first draft not be removed).
NOTE: AccessControlManagerImplTest#testTestSessionGetPrivileges would still fail (blocking issues is OAK-766)
was (Author: anchela):
patch 1:
define built-in default policy that grants
read access for node types, namespace and privileges and adjust permission evaluation accordingly (note: isGranted is not yet adjusted, policy can in this first draft not be removed).
> Accessibility of NodeTypes, Namespaces and Privileges
> -----------------------------------------------------
>
> Key: OAK-787
> URL: https://issues.apache.org/jira/browse/OAK-787
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: core
> Reporter: angela
> Assignee: angela
> Attachments: OAK-787.patch
>
>
> in jackrabbit-core node types, namespaces and privileges were stored
> separated from the repository content in the file system. accessibility
> of that part of the repository was therefore never managed by the
> regular item access in jackrabbit.
> now, as of oak all of them are stored and accessed in the repository
> and are consequently affected by regular item read access which
> basically breaks backwards compatibility.
> we should define means of asserting backwards compatible behavior.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira