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

Incremental AD synchronisation silently ignores remote deletions if the user does not have admin privileges

XMLWordPrintable

      Symptoms

      Users deletions in an AD are not propagated to Crowd by (apparently successful) incremental synchronisation if the connector binds to AD using unprivileged credentials.

      Steps to reproduce

      1. Create an unprivileged user in AD, e.g., CN=UnprivUser,OU=People,DC=sydney,DC=atlassian,DC=com
      2. Set up an AD LDAP connector in Crowd, use the unprivileged user credentials to connect to AD.
      3. Do a full synchronisation
      4. Create a new ephemeral user in AD using the AD console or any other tool different from Crowd itself.
      5. Synchronise again. An incremental synchronisation successfully propagates the new user to Crowd. Verify the new user actually exists in Crowd with the user browser.
      6. Delete the ephemeral user from AD using the AD console or any other tool different from Crowd itself.
      7. Synchronise again.

      Expected behaviour

      Either the deletion is propagated from AD to Crowd if possible (fallback to full sync?), or the user is notified about the failure to complete an incremental synchronisation (see CWD-2714).

      Actual behaviour

      The deletion is not propagated from AD to Crowd. The synchronisation completes without any error message, logs contain "deleting [ 0 ] users", and the ephemeral user still appears in the user browser.

            [CWD-3093] Incremental AD synchronisation silently ignores remote deletions if the user does not have admin privileges

            Trix added a comment -

            The synchronisation account does not have to be an administrator to retrieve the Deleted Objects.

            Using the Dirsync method, the account needs to have the Replicate Directory changes right. This can be delegated to an otherwise non-elevated account: https://support.microsoft.com/en-au/kb/303972

            LDAP can then use the Dirsync control to search and show deleted objects. https://msdn.microsoft.com/en-us/library/ms677626.aspx

            It is also possible to directly modify the permissions on the Deleted Objects container, although this method is less preferred. https://support.microsoft.com/en-au/kb/892806

            Trix added a comment - The synchronisation account does not have to be an administrator to retrieve the Deleted Objects. Using the Dirsync method, the account needs to have the Replicate Directory changes right. This can be delegated to an otherwise non-elevated account: https://support.microsoft.com/en-au/kb/303972 LDAP can then use the Dirsync control to search and show deleted objects. https://msdn.microsoft.com/en-us/library/ms677626.aspx It is also possible to directly modify the permissions on the Deleted Objects container, although this method is less preferred. https://support.microsoft.com/en-au/kb/892806

              pszczepanik Szczepan (Inactive)
              dberrueta Diego Berrueta
              Affected customers:
              18 This affects my team
              Watchers:
              24 Start watching this issue

                Created:
                Updated:
                Resolved: