-
Bug
-
Resolution: Fixed
-
Medium
-
2.3.4, 2.5.2
How to Reproduce:
- Create 2 groups in LDAP:
- Group1
- Group2
- Assign membership attributes to each Group as per below:
- Group1
- member: Group2
- member: UserA
- Group2
- member: UserB
- Group1
- Set up a Delegated Authentication Directory in Crowd, with the Use Nested Groups and Sync Group Memberships options checked
- Login to Crowd using UserB (Notice that only Group2 is synced, Group1 is not synced even though Group2 is child of Group1).
- Login with UserA this time (Notice that Group1 is also synced now, but if you try to check on the Nested Members of Group1, you'll find that only UserA is a Nested/Direct Member of Group1. What happened to UserB? UserB is only a member of Group2.
This indicates that the Nested Groups functionality of Delegated Authentication Directory does not really work at all.
- duplicates
-
CWD-2719 LDAP Delegate: Also sync parent groups
- Closed
- is duplicated by
-
CWD-2719 LDAP Delegate: Also sync parent groups
- Closed
- relates to
-
CONFCLOUD-27032 Nested Group option on Delegated LDAP for Confluence 3.5 and above
- Closed
-
CONFSERVER-27032 Nested Group option on Delegated LDAP for Confluence 3.5 and above
- Closed
-
CWD-1334 Support Nested Groups when importing User, Groups and Memberships into a Delegated Directory.
- Gathering Interest
- Testing discovered
-
CWD-3136 'Nested groups' setting is ignored by delegated authentication directories
-
- Closed
-