-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 6.0.5
-
Component/s: Directories
-
11
-
Severity 3 - Minor
-
36
Issue Summary
Users in the AD nested group are not synced after upgrading Confluence from any version prior to 8.5.x to 9.x.x
Steps to Reproduce
- Setup Microsoft AD
- Create users in the AD
- Create a parent group and a child group.
- Add members to the child group.
- Add the child group as a member of the parent group.
- Install and configure 9.2.1 Confluence
- Configure the user directory in Confluence to use the Microsoft AD created earlier.
- In the User Membership Attribute field, add memberOf:1.2.840.113556.1.4.1941: and check the boxes for When finding the user's group membership and When finding the members of a group under Use the User Membership Attribute.
- Save and test
- Perform synchronization with the user directory.
- The users in the parent group are not visible.
Expected Results
The users in the parent group should be visible.
Actual Results
The users in the parent group are not visible.
Workaround
This is happening due to a change in Crowd sync on Crowd 5.3.0; Crowd 5.3 Upgrade Notes; LDAP synchronization improvements. The workaround is to disable the new sync:
- Stop Confluence
- Take a backup of <InstallHome>/bin/setenv.sh file
- Add the below JVM parameter just above the export CATALINA_OPTS line
CATALINA_OPTS="-Dcrowd.use.legacy.ad.membership.sync=true ${CATALINA_OPTS}" - Start Confluence
- Perform a synchronization
- is related to
-
BSERV-19883 Using LDAP_MATCHING_RULE_IN_CHAIN OID for nested group membership stopped working
-
- Closed
-
- links to