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 "Amit Jain (JIRA)" <ji...@apache.org> on 2014/11/10 06:50:35 UTC

[jira] [Closed] (OAK-2245) UserImporter should always set the rep:authorizableID

     [ https://issues.apache.org/jira/browse/OAK-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amit Jain closed OAK-2245.
--------------------------

Bulk close for 1.1.2

> UserImporter should always set the rep:authorizableID
> -----------------------------------------------------
>
>                 Key: OAK-2245
>                 URL: https://issues.apache.org/jira/browse/OAK-2245
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: angela
>            Assignee: angela
>             Fix For: 1.1.2
>
>         Attachments: OAK-2245.patch, oak-2245-additional-tests.patch
>
>
> upon XML import of user/group nodes the UserImporter currently doesn't enforce the creation of rep:authorizableID which has been introduced with Oak 1.0.
> while this allows to import JR 2.x content packages as they are, it will cause the import to fail in case of uuid-conflicts with existing authorizables at a different location.
> for this reason and in order to make sure that imported user/group content always has the authorizableID set, we should change the user importer to verify that an authorizable id property has been imported.



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