-
Bug
-
Resolution: Fixed
-
Medium
-
6.15.4, 6.15.7
-
2
-
Severity 1 - Critical
-
Summary
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 CONFSERVER-28621
Environment
- 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
Steps to Reproduce
- 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:
(&(objectclass=inetorgperson)(cn=dummynonexistentuser))
- 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)
Notes
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
Workaround
- 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.
- is a regression of
-
CONFSERVER-28621 User Loses all Local Group Memberships If LDAP Sync is Unable to find the User, but the User appears again in subsequent syncs
- Closed
- is cloned from
-
CONFSERVER-28621 User Loses all Local Group Memberships If LDAP Sync is Unable to find the User, but the User appears again in subsequent syncs
- Closed
- is related to
-
CWD-4179 synchronization of large groups in Crowd timeout and starts to remove users from cache
- Closed
-
CWD-4849 User loses all local group memberships if LDAP sync is unable to find the user, but the user appears again in subsequent syncs
- Long Term Backlog
-
KRAK-258 Loading...
- relates to
-
JRASERVER-24937 When a user is deleted in AD or Crowd, JIRA could keep the user in JIRA as an inactive user
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...