Status: Closed (View Workflow)
Affects Version/s: 6.15.4, 6.15.7
Fix Version/s: 7.0.1
Component/s: User - Management
Support reference count:2
Symptom Severity:Severity 1 - Critical
Bug Fix Policy:
When users are filtered out/synchronized out from Confluence and re-synchronized back into Confluence, they will lose their Local Group Membership.
This is a regression from
- Confluence 6.15x
- Cannot replicate this issue on 6.14.0. Expired users are shown as "Disabled"
- Unable to replicate on Confluence 7.0.1-beta1
- Add a connection to LDAP in Confluence Admin >> User Directories with the Read Only, with Local Groups option
- Sync the directory and make sure that LDAP users are returned
- Add 1 LDAP user to a local group (membership)
- Change the User Object Filter in the directory's configuration in Confluence Admin >> User Directories to a dummy filter, such as the following:
- Sync the directory again (Notice that the LDAP users are missing)
- Revert the User Object Filter to the previous working filter
- Sync the directory again (notice that the LDAP users are back, but their local group memberships are gone)
This issue could happen if expired users get filtered out from Confluence due to the "Filter out expired users" settings, and re-synchronized back into Confluence after their expiry has been refreshed
- Restore the instance's database backup to a new database (i.e. not production) prior to the point where memberships were lost.
- Follow the instructions in step 1 of Migrating Local Group Memberships Between Directories to generate a CSV file of users and their memberships.
- Run through the rest of the instructions in that KB article to populate the production instance's group memberships.