AD Incremental Synchronisation will leave the user map cache in an inconsistent state of a user is removed from AD

XMLWordPrintable

    • Type: Bug
    • Resolution: Invalid
    • Priority: Medium
    • None
    • Affects Version/s: 2.8.0-OD-6, 2.8.0-OD-6-JIRA-01
    • Component/s: Caching, Directory - LDAP
    • None

      Reproduction Steps

      1. Create an Active Directory in JIRA and specify the user filter with a "memberOf" attribute, after saving the directory full sync will be run.
      2. Add a user to AD and set the appropriate memberOf attribute specified in the filter used in step 1.
      3. Run incremental sync - because the new user satisfies the filter specified in step 1, they will be added to the userMap cache and to the internal directory.
      4. Remove the user from AD.
      5. BUG Run Inc Sync - the user will be removed from the internal directory but not from userMap leaving it in an inconsistent state. This will in turn cause problems for further incremental synchronisation operations until the cache is reconstituted via a full sync operation.

      Crowd should make sure to update the cache properly so it reflects user removal.

            Assignee:
            Arkadiusz Glowacki (Inactive)
            Reporter:
            Oswaldo Hernandez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: