[
https://issues.apache.org/jira/browse/OAK-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14189768#comment-14189768
]
angela commented on OAK-2245:
-----------------------------
[~tripod], thanks a lot.
regarding the problem you found: a jr2 user node that has been renamed is
broken anyway. importing this node as is will in any case fail as the uuid
doesn't match the id (this is verified in the commit hook) and in jr2 the only
way to obtain the ID string was the node name... so, i don't consider this a
realistic scenario. it was different if simply moving (but not renaming) the
node would have the same effect. wdyt?
> 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
> 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)
