Overview of Caching

Caching is used to store run-time authentication and authorization rules, which can be expensive to calculate.

In Crowd, data caching occurs in three main areas:

  • Application caches in the applications that are connected to Crowd – Applications such as JIRA, Confluence and Bamboo can store user, group and role data in a local cache. This helps improve the performance of Crowd, since these applications do not have to repeatedly request information from Crowd. Generally it is not necessary to configure application caching, although this depends on the size of your application deployments. You can set the options for application caching in the cache configuration file for that application. See Configuring Caching for an Application.
  • An authorization cache on the Crowd server – To improve performance, Crowd can store users' authentication and per-application permissions in a local cache for a specified period. You can enable or disable this cache via an option on the 'General Options' screen in the Crowd Administration Console. See Authorization Caching.
  • LDAP directory caches in the Crowd database – The Crowd database keeps an up-to-date cache of all user and group information from the LDAP directory. You can configure this cache on the directory connector screen. See Configuring Caching for an LDAP Directory.

This diagram gives a conceptual overview of the caches described above:

LDAPCaching-2.1
RELATED TOPICS

Crowd Documentation

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport