MS Active Directory Group Membership not updating

Question

We have the Jira instance integrated with Microsoft Active Directory (Read Only, with Local Groups).

When we added a new member to a group Active Directory, Jira did not refresh the list of members from that group.

We tried a manual sync, but don't work.

No errors in the logs.

We use JIRA v6.3.4a

Aron Felberbaum · Answer

There was a local group with the same name as a local group. Since there is an existing local group, the group membership of the AD group is not being pulled. Even after deleting the local group, the AD group membership is still not updated because each membership per user on that group is saved in JIRA and is tagged as "local" (cwd_group.local = 1). More details on the issue:https://confluence.atlassian.com/display/JIRAKB/Membership+For+Group+Is+Not+Updated+After+Synchronisation

Piotr Klimkowski · Answer

From the log at hand - I don't know, ask support maybe ?
Maybe turn the debug logging on for crowd, but it will be huge.

Aron Felberbaum · Answer

I disabled incremental sync and members are still not added.

2015-02-06 09:36:51,871 atlassian-scheduler-quartz1.clustered_Worker-2 INFO ServiceRunner     [atlassian.crowd.directory.DbCachingRemoteDirectory] synchronisation for directory [ 10002 ] starting
2015-02-06 09:36:51,981 CrowdUsnChangedCacheRefresher:thread-2 INFO ServiceRunner     [directory.ldap.cache.UsnChangedCacheRefresher] found [ 3 ] remote groups in [ 110ms ]
2015-02-06 09:37:22,404 CrowdUsnChangedCacheRefresher:thread-1 INFO ServiceRunner     [directory.ldap.cache.UsnChangedCacheRefresher] found [ 5730 ] remote users in [ 30533ms ]
2015-02-06 09:37:22,591 atlassian-scheduler-quartz1.clustered_Worker-2 INFO ServiceRunner     [atlassian.crowd.directory.DbCachingRemoteChangeOperations] scanned and compared [ 5730 ] users for delete in DB cache in [ 172ms ]
2015-02-06 09:37:22,591 atlassian-scheduler-quartz1.clustered_Worker-2 INFO ServiceRunner     [atlassian.crowd.directory.DbCachingRemoteChangeOperations] scanned for deleted users in [ 172ms ]
2015-02-06 09:37:22,591 atlassian-scheduler-quartz1.clustered_Worker-2 INFO ServiceRunner     [atlassian.crowd.directory.DbCachingRemoteChangeOperations] scanning [ 5730 ] users to add or update
2015-02-06 09:37:22,607 atlassian-scheduler-quartz1.clustered_Worker-2 INFO ServiceRunner     [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] scanned and compared [ 5730 ] users for update in DB cache in [ 16ms ]
2015-02-06 09:37:22,607 atlassian-scheduler-quartz1.clustered_Worker-2 INFO ServiceRunner     [atlassian.crowd.directory.DbCachingRemoteChangeOperations] updating [ 7 ] users
2015-02-06 09:37:23,185 atlassian-scheduler-quartz1.clustered_Worker-2 INFO ServiceRunner     [atlassian.crowd.directory.DbCachingRemoteChangeOperations] updated [ 7 ] users in [ 578ms ]
2015-02-06 09:37:23,185 atlassian-scheduler-quartz1.clustered_Worker-2 INFO ServiceRunner     [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] synchronised [ 5730 ] users in [ 594ms ]
2015-02-06 09:37:23,185 atlassian-scheduler-quartz1.clustered_Worker-2 INFO ServiceRunner     [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] scanning [ 3 ] groups to add or update
2015-02-06 09:37:23,232 atlassian-scheduler-quartz1.clustered_Worker-2 INFO ServiceRunner     [atlassian.crowd.directory.DbCachingRemoteChangeOperations] scanned and compared [ 3 ] groups for update in DB cache in [ 47ms ]
2015-02-06 09:37:23,232 atlassian-scheduler-quartz1.clustered_Worker-2 INFO ServiceRunner     [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] synchronized [ 3 ] groups in [ 47ms ]
2015-02-06 09:37:23,232 atlassian-scheduler-quartz1.clustered_Worker-2 INFO ServiceRunner     [atlassian.crowd.directory.DbCachingRemoteChangeOperations] scanned and compared [ 3 ] groups for delete in DB cache in [ 0ms ]
2015-02-06 09:37:23,544 atlassian-scheduler-quartz1.clustered_Worker-2 INFO ServiceRunner     [atlassian.crowd.directory.DbCachingRemoteChangeOperations] removed [ 1 ] user members from [ Jira Developers ] in [ 281ms ]
2015-02-06 09:37:23,544 atlassian-scheduler-quartz1.clustered_Worker-2 INFO ServiceRunner     [atlassian.crowd.directory.DbCachingRemoteDirectory] FULL synchronisation complete for directory [ 10002 ] in [ 31673ms ]