Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. 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

      Steps to Reproduce

      1. Add a connection to LDAP in Confluence Admin >> User Directories with the Read Only, with Local Groups option
      2. Sync the directory and make sure that LDAP users are returned
      3. Add 1 LDAP user to a local group (membership)
      4. 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))
        
      5. Sync the directory again (Notice that the LDAP users are missing)
      6. Revert the User Object Filter to the previous working filter
      7. Sync the directory again (notice that the LDAP users are back, but their local group memberships are gone)

      Workaround

      1. Restore the instance's database backup to a new database (i.e. not production) prior to the point where memberships were lost.
      2. Follow the instructions in step 1 of Migrating Local Group Memberships Between Directories to generate a CSV file of users and their memberships.
      3. Run through the rest of the instructions in that KB article to populate the production instance's group memberships.

            [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

            Sneha Anand made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 879518 ]

            For anyone who is still experiencing this issue, we were able to resolve this by disabling the Incremental Sync option in the Active Directory sync settings. Doing this triggered a full sync instead of an incremental sync, and the group memberships for the users which were having the problem re-appeared. 

            We have a fairly small organization (~200 Users), so we made the decision to leave the incremental sync off as it took no more time to complete. In theory you should be able to re-enable it after the full sync, and it would be happy again.

            Brennan Norwood added a comment - For anyone who is still experiencing this issue, we were able to resolve this by disabling the Incremental Sync option in the Active Directory sync settings. Doing this triggered a full sync instead of an incremental sync, and the group memberships for the users which were having the problem re-appeared.  We have a fairly small organization (~200 Users), so we made the decision to leave the incremental sync off as it took no more time to complete. In theory you should be able to re-enable it after the full sync, and it would be happy again.
            Monique Khairuliana (Inactive) made changes -
            Link Original: This issue is a regression of CONFSERVER-58751 [ CONFSERVER-58751 ]
            Monique Khairuliana (Inactive) made changes -
            Link New: This issue has a regression in CONFSERVER-58751 [ CONFSERVER-58751 ]
            Monique Khairuliana (Inactive) made changes -
            Link New: This issue is a regression of CONFSERVER-58751 [ CONFSERVER-58751 ]
            Monique Khairuliana (Inactive) made changes -
            Link New: This issue was cloned as CONFSERVER-58751 [ CONFSERVER-58751 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Bug Workflow v3 [ 2879883 ] New: CONFSERVER Bug Workflow v4 [ 3003609 ]
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2787746 ] New: JAC Bug Workflow v3 [ 2879883 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JAC Bug Workflow [ 2737232 ] New: JAC Bug Workflow v2 [ 2787746 ]
            Owen made changes -
            Symptom Severity Original: Critical [ 14430 ] New: Severity 1 - Critical [ 15830 ]

              fxu Feng Xu (Inactive)
              fsim Foo Sim (Inactive)
              Affected customers:
              79 This affects my team
              Watchers:
              85 Start watching this issue

                Created:
                Updated:
                Resolved: