At present, Crowd-integrated clients such as JIRA or Confluence, will not see changes made in Crowd until their Crowd cache expires.
This default value is set to 1 hour (3600 seconds) in the application's WEB-INF/classes/crowd-ehcache.xml file. User can reduce these values to cause faster updates (e.g. 300 seconds). However, this may cause serious performance degradation (especially in JIRA).
Changes made to users and groups via the Crowd client application (e.g. JIRA) will be immediately available in the application in Crowd.
In the future, we need to have Crowd send event notifications to these client applications for smaller cache updates. This will not only resolve this problem but help with Crowdified application performance as well.
- causes
-
CWD-1796 Crowd Integration Cache for JIRA is not updated
- Closed
- details
-
CWD-2505 Document REST api changes in EAC
- Closed
-
CWD-2518 Disable incremental sync and show a warning if the remote application contains remote directories that are not cached
- Closed
-
CWD-2519 Enable UI for incremental synchronisation
- Closed
- is duplicated by
-
CWD-2405 Allow Crowd's LDAP DB cache to have an attribute equivalent to USNChanged
- Closed
- is related to
-
CWD-2759 Force application sync on add user event
- Under Consideration
- relates to
-
JRASERVER-16493 Add to Jira Admin console a button to refresh the User Repository cache (eg. Crowd's cache)
- Closed