Group and User Management Related Changes Made in LDAP are Not Reflected in Confluence
Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
It takes 24 hours for changes such as group renaming in the LDAP directory to show in Confluence. The changes are visible in Crowd almost instantaneously (as configured) but Confluence doesn't seem to react to those changes.
Flushing Confluence's cache from "Administration->Cache Statistics->Flush All" console, appears to make those changes visible in Confluence immediately.
Cause
Logs report the following error:
2010-07-09 15:37:02,621 http-8095-5 ERROR [sf.ehcache.store.DiskStore] com.atlassian.crowd.integration.directory.caching-group-names360450Cache: Could not read disk store element for key all.names.key. Error was com.atlassian.crowd.integration.directory.caching-group-names360450 Cache: The Disk store is not active.
net.sf.ehcache.CacheException: com.atlassian.crowd.integration.directory.caching-group-names360450 Cache: The Disk store is not active.
at net.sf.ehcache.store.DiskStore.checkActive(DiskStore.java:208)
at net.sf.ehcache.store.DiskStore.get(DiskStore.java:219)
at net.sf.ehcache.Cache.searchInDiskStore(Cache.java:845)
at net.sf.ehcache.Cache.get(Cache.java:656)
at net.sf.ehcache.Cache.get(Cache.java:631)
at com.atlassian.crowd.integration.directory.cache.DefaultDirectoryCache.getAllEntityNames(DefaultDirectoryCache.java:325)
at com.atlassian.crowd.integration.directory.cache.DefaultDirectoryCache.storeEntity(DefaultDirectoryCache.java:360)
at com.atlassian.crowd.integration.directory.cache.LDAPDirectoryCache.storeGroup(LDAPDirectoryCache.java:86)
at com.atlassian.crowd.integration.directory.cache.MicrosoftActiveDirectoryCache.storeGroup(MicrosoftActiveDirectoryCache.java:151)
at com.atlassian.crowd.integration.directory.cache.CachingLDAPDirectory.findAllGroups(CachingLDAPDirectory.java:932)
at com.atlassian.crowd.integration.directory.cache.CachingLDAPDirectory.searchGroups(CachingLDAPDirectory.java:979)
at com.atlassian.crowd.manager.directory.DirectoryManagerGeneric.searchGroups(DirectoryManagerGeneric.java:389)
Resolution
The suggested step to copy CROWD/client/conf/crowd-ehcache.xml to CONFLUENCE/confluence/WEB-INF/classes/crowd-ehcache.xml has not been completed successfully, and the above file is still using Confluence's default crowd-encache.xml not the one copied over from Crowd as recommended in point 3 in this document.
Ensure that the above file has been copied across correctly and then restart the applications.
Was this helpful?