[jira] [Comment Edited] (OAK-2740) TreeTypeProvider treates optimized node type definition info as Ac-Content

["angela (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OAK-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487501#comment-14487501 ] 

angela edited comment on OAK-2740 at 4/9/15 3:43 PM:
-----------------------------------------------------

the user-import test provided by marius that allowed me to reproduce the problem (which some extra refactoring to allow for non-admin imports).
this is just for completeness; i will create an different jira issue for these user-importer tests as they are no longer relevant for this issue (see OAK-2742)... dedicated test-case that illustrates the root-cause of this bug will follow (attached as OAK_2740_test.patch).


was (Author: anchela):
the user-import test provided by marius that allowed me to reproduce the problem (which some extra refactoring to allow for non-admin imports).
this is just for completeness; i will create an different jira issue for these user-importer tests as they are no longer relevant for this issue... dedicated test-case that illustrates the root-cause of this bug will follow.

> TreeTypeProvider treates optimized node type definition info as Ac-Content
> --------------------------------------------------------------------------
>
>                 Key: OAK-2740
>                 URL: https://issues.apache.org/jira/browse/OAK-2740
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: angela
>            Assignee: angela
>            Priority: Blocker
>         Attachments: OAK-2740.patch, OAK-2740_importTests.patch, OAK-2740_test.patch
>
>
> while investigating a bug reported by [~teofili] and [~mpetria] that cause group-import with policy node to fail when run with non-administrative session, i found that the {{TreeTypeProvider}} wrongly identifies the optimized item definition information stored with the node types (e.g. {{/jcr:system/jcr:nodeTypes/rep:AccessControllable/rep:namedChildNodeDefinitions/rep:policy}} ) as access control content and thus doesn't read it properly when using a session that doesn't have jcr:readAccessControl privilege at /jcr:system/jcr:nodeTypes.
> the effect of this bug is as follows:
> the internal calculation of the effective node type and thus item definitions will not work properly for {{rep:policy}} nodes (and similar) as the editing session cannot read the full (oak internal) node type definition as stored below {{/jcr:system/jcr:nodeTypes}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)