Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-26458

Synchronization of users that are added to a particular AD group that is configured to automatically become JIRA users doesn't work after the initial synch

XMLWordPrintable

      Summary

      We have our Jira instance setup to synchronize with Active Directory such that any users that are added to a particular AD group are supposed to automatically become Jira users. When we initially configured the user directory, the synchronization worked perfectly and all users were able to login to Jira. However, when a new user joined the AD group, it is not automatically created in JIRA.

      Steps to Reproduce

      The following LDAP User Filter is used on the User Directory:

      "ldap.user.filter": "(&(objectCategory=Person)(memberOf=CN=newgrp,CN=Users,DC=company,DC=local))"
      

      Expected Results

      All the users that are members of the newgrp after the synchronization are automatically added to the jira-users group.

      Actual Results

      For the first time the directory is synchronized, everything works fine. However, if a user is added to the newgrp directory after the first synchronization, it is not automatically added to Jira, instead we can see this message in the atlassian-jira.log:

      2011-12-06 10:05:41,016 QuartzWorker-1 WARN ServiceRunner     [atlassian.crowd.directory.DbCachingRemoteChangeOperations] Could not add the following missing users to group [ newgrp ]: [johndoe]
      

      Workaround

      The workaround for this situation is to go into your Advanced Settings in your user Directory and uncheck "Enable Incremental Synchronization" as per Connecting to an LDAP Directory.

              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              cgauterio Clarissa Gauterio (Inactive)
              Votes:
              20 Vote for this issue
              Watchers:
              36 Start watching this issue

                Created:
                Updated:
                Resolved: