You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marius Petria (JIRA)" <ji...@apache.org> on 2014/11/04 07:47:34 UTC

[jira] [Commented] (JCRVLT-71) Allow creation of ancestor user nodes when they are not explicitly included in a filter

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

Marius Petria commented on JCRVLT-71:
-------------------------------------

Note that JCRVLT-62 is also about options to control autocreation of parent nodes in general. Maybe the same mechanism can be used also for users.

> Allow creation of ancestor user nodes when they are not explicitly included in a filter
> ---------------------------------------------------------------------------------------
>
>                 Key: JCRVLT-71
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-71
>             Project: Jackrabbit FileVault
>          Issue Type: Bug
>            Reporter: Marius Petria
>
> JCRVLT-64 restricted the creation of user nodes only to the case when they are explicitly included in the filter. This is in practice more secure but one should also have the option to lower this guard and be more robust. 
> The use case I have in mind is creating exact replicas of user content in two instances. There is no security concern that users are autocreated as in the end the goal is to have identical instances.
> We could have an option to allow autocreation of user nodes as this will make user creation more aligned with regular node creation.



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