[
https://issues.apache.org/jira/browse/JCRVLT-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388212#comment-14388212
]
Anshika Agarwal commented on JCRVLT-86:
---------------------------------------
Investigation: The issue is occurring in the addMembers API of
JackrabbitUserManagementb class. In order to retrieve the authorizable of the
member that needs to be added, this API first retrieves the node of the member
and relies on the value of node name instead of the authorizable Id to carry
out uMgr.getAuthorizable(authId). Can we have this changed to rely on
authorizable id instead.
> JackrabbitUserManagement is unable to add member to existing group if the
> member node name is different from its principal id.
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: JCRVLT-86
> URL: https://issues.apache.org/jira/browse/JCRVLT-86
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Affects Versions: 3.1.18
> Reporter: Anshika Agarwal
> Labels: usermanager
> Fix For: 3.1.18
>
>
> I have a use case of adding members to a common group via multiple packages.
> In order to achieve this, I have specified the same filter in both the
> packages with mode='merge' attribute.
> This works well as long as the group I am adding as a member has an
> authorizable ID that is same as its node name. However, if the node name of
> the group is different from the authorizable ID, the group does not get added
> as a member. The following warning log is seen at the time of package
> installation:
> org.apache.jackrabbit.vault.fs.spi.impl.jcr20.JackrabbitUserManagement unable
> to add authorizable 'forms-manager-administrator' to group 'forms-users'. No
> such authorizable.
> Expected: The addMembers API of JackrabbitUserManagement should support
> members having a node name different from the authorizable id.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
