Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-3606

Incremental sync does not correctly pick LDAP group rename

XMLWordPrintable

      Steps to reproduce

      1. In an AD server, create a user deke and a group (e.g. astronauts). Add deke to the group.
      2. In Crowd, create a LDAP connector and point it to AD, hen Sync
      3. Verify that triggered a sync and deke's group memberships show astronauts
      4. Rename astronauts to retired-astronauts
      5. Trigger a sync (should be an incremental sync)
      6. Check deke's group memberships in Crowd

      Observed

      deke is a member of astronauts and retired-astronauts.

      Expected

      deke is only a member of retired-astronauts

      Notes

      • A full sync restores the consistency.
      • This can be reproduced with a primary group membership, not just with a regular membership.

          Form Name

            [CWD-3606] Incremental sync does not correctly pick LDAP group rename

            Alain Moran added a comment -

            Disabling and re-enabling the cache in the directory definition also seems to resolve this.

            Alain Moran added a comment - Disabling and re-enabling the cache in the directory definition also seems to resolve this.

            Diego Berrueta added a comment -

            As a workaround, I've confirmed that a full sync restores the consistency of the memberships. Therefore, until Crowd implements support to pick up group renames from LDAP directories, it is recommended to do a full sync after any group renaming operation.

            Diego Berrueta added a comment - As a workaround, I've confirmed that a full sync restores the consistency of the memberships. Therefore, until Crowd implements support to pick up group renames from LDAP directories, it is recommended to do a full sync after any group renaming operation.

              Unassigned Unassigned
              ckrieger Caspar Krieger (Inactive)
              Affected customers:
              12 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated: