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 "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2014/12/19 00:29:13 UTC

[jira] [Resolved] (OAK-2367) Importing a group with random node name and members fails.

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

Tobias Bocanegra resolved OAK-2367.
-----------------------------------
    Resolution: Fixed

fixed the problem in r1646579 by using the group's path to keep track of the memberships to be imported.

> Importing a group with random node name and members fails.
> ----------------------------------------------------------
>
>                 Key: OAK-2367
>                 URL: https://issues.apache.org/jira/browse/OAK-2367
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 1.2, 1.1.3
>            Reporter: Tobias Bocanegra
>            Assignee: Tobias Bocanegra
>             Fix For: 1.1.4
>
>
> When importing a group via SysView that has a node name that does not match the group name and has members, it might fail if {{rep:members}} property is processed before the {{rep:authorizableId}} property. The problem is that the internal {{Membership}} tracking class is initialized too early with the wrong, preliminary, id.



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