-
Bug
-
Resolution: Fixed
-
Highest
-
7.11.0, 7.11.1, 7.11.2
-
30
-
Severity 2 - Major
-
189
-
Issue Summary
User Directory Synchronization never triggered as per the schedule Interval in Confluence 7.11.0, whereas the same configuration works properly in Confluence version 7.10 and the schedule kicks the User directory sync as per the scheduled interval.
However, manual sync works as expected in Confluence version 7.11
Environment
- Confluence 7.11.0
- Used Crowd User Directory and Active Directory
Steps to Reproduce
- Install a fresh Confluence 7.11.0 or Upgrade to 7.11.0
- Configured the Crowd User Directory and set Synchronization Interval (minutes): to any number. I used 5 min,
- Test the Connection and save the settings.
- User directory sync will not get triggered until we triggered manually.
- As per the expectation, the schedule should trigger the User Directory sync as per the scheduled time but the user directory sync never triggers, only manual sync works here.
Expected Results
User directory sync should be triggered as per the scheduled time.
Actual Results
The atlassian-confluence-security.log shows only manual Sync logs_._
file:
2021-02-12 09:50:39,733 INFO [http-nio-27110-exec-10] [embedded.admin.list.DirectoriesController] sync User directory synchronisation requested: [ Crowd Server ], type: [ CROWD ] 2021-02-12 09:50:39,861 INFO [Caesium-1-4] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache FULL synchronisation for directory [ 98306 ] starting 2021-02-12 09:50:40,031 INFO [Caesium-1-4] [directory.ldap.cache.RemoteDirectoryCacheRefresher] findAllRemoteUsers found [ 2 ] remote users in [ 68 ms ] 2021-02-12 09:50:40,037 INFO [Caesium-1-4] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] deleteCachedUsersNotIn scanned and compared [ 2 ] users for delete in DB cache in [ 5ms ] 2021-02-12 09:50:40,037 INFO [Caesium-1-4] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] deleteCachedUsersNotIn scanned for deleted users in [ 5ms ] 2021-02-12 09:50:40,040 INFO [Caesium-1-4] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] getUsersToAddAndUpdate scanning [ 2 ] users to add or update 2021-02-12 09:50:40,044 INFO [Caesium-1-4] [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] addOrUpdateCachedUsers scanned and compared [ 2 ] users for update in DB cache in [ 6ms ] 2021-02-12 09:50:40,046 INFO [Caesium-1-4] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] addUsers adding [ 2 ] users 2021-02-12 09:50:40,143 INFO [Caesium-1-4] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] addUsers added [ 2 ] users successfully in [ 97ms ] 2021-02-12 09:50:40,144 INFO [Caesium-1-4] [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] addOrUpdateCachedUsers synchronised [ 2 ] users in [ 106ms ] 2021-02-12 09:50:40,219 INFO [Caesium-1-4] [directory.ldap.cache.RemoteDirectoryCacheRefresher] findAllRemoteGroups found [ 1 ] remote groups in [ 73 ms ] 2021-02-12 09:50:40,225 INFO [Caesium-1-4] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] determineGroupsToRemoveByName scanned and compared [ 1 ] groups for delete in DB cache in [ 3ms ] 2021-02-12 09:50:40,226 INFO [Caesium-1-4] [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] addOrUpdateCachedGroups scanning [ 1 ] groups to add or update 2021-02-12 09:50:40,228 INFO [Caesium-1-4] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] findGroupsToUpdate scanned and compared [ 1 ] groups for update in DB cache in [ 2ms ] 2021-02-12 09:50:40,242 INFO [Caesium-1-4] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] addGroups added [ 1 ] groups successfully in [ 10ms ] 2021-02-12 09:50:40,243 INFO [Caesium-1-4] [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] addOrUpdateCachedGroups synchronized [ 1 ] groups in [ 17ms ] 2021-02-12 09:50:40,459 INFO [Caesium-1-4] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache FULL synchronisation complete for directory [ 98306 ] in [ 624ms ]
User directory page also shows the last manual Sync time
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
[CONFSERVER-61194] User directory synchronization never trigger based on the Interval on Confluence 7.11.0
A fix for this issue is available to Server and Data Center customers in Confluence 7.11.3
Upgrade now or check out the Release Notes to see what other issues are resolved.
A fix for this issue is available to Server and Data Center customers in Confluence 7.12.0
Upgrade now or check out the Release Notes to see what other issues are resolved.
@Lai Feng Min
You need 7.11.2 for the Disable/Enable Workaround.
hi @Hasnae
Can advise when will the final fix be available?
Since the Disable/Enable does not work for my Confluence DC 7.11.1, is it possible to manually create this AD-sync job under the Scheduled Jobs?
I have only one local directory and one AD user directory. Even after disabling and enabling the AD user directory, the scheduled sync does not take place as expected.
Thanks for the feedback, we have identified the new root cause and a final fix is on the way.
Apologies for the inconvenience.
We have the same error on Confluence 8.5.7. Please could you check if there's a regression about this bug?
Thanks in advance,
Fabio