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/01/23 19:31:12 UTC
[jira] [Commented] (OAK-443) UserInitializer causes repository
traversal
[ https://issues.apache.org/jira/browse/OAK-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560915#comment-13560915 ]
angela commented on OAK-443:
----------------------------
> All tests pass but everything extending AbstractSecurityTest doesn't use any kind of indexes for the tests.
> I would have liked to add the p2 ones (Property2IndexHookProvider, Property2IndexProvider) to the tests but
> then some of them start failing (the ExternalLoginModuleTest and another one)
i stumbled of the missing index configuration as well... actually, because i was wondering whe
the uniqueness violation of rep:principalName was not detected when i save a ac-policy (-> see OAK-396).
in other words: i would love to have that change in the AbstractSecurityTest but it requires that OAK-396
is being fixed... since OAK-396 is starting to block me, that would be a wise thing anyway :-)
as far as the failing user tests are concerned i will fix them right away.
regarding:
> 2. The UserInitializer will now use a Root instance that has both a Property2IndexProvider hardcoded
> as well as a Property2IndexHookProvider.
that doesn't look too nice to me... but fine with me as a temporary solution to get rid of this issue.
> UserInitializer causes repository traversal
> -------------------------------------------
>
> Key: OAK-443
> URL: https://issues.apache.org/jira/browse/OAK-443
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Marcel Reutegger
> Attachments: OAK-443.patch
>
>
> UserInitializer operates on a RootImpl without QueryIndexProvider, which results in a traversal of the complete content when an authorizable is looked up.
--
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