This page last changed on Apr 02, 2007 by rosie@atlassian.com.

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

It is recommended that caching be turned off during development cycles, and re-enabled for production use.

In Crowd, caching occurs in two main areas:

  • The Crowd server itself — certain parts of the Crowd Administration Console application are stored in a local cache to improve performance.
  • The applications that are connected to Crowd — e.g. JIRA, Confluence and Bamboo. These applications store users, groups and role data in a local cache, which 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.
To fine-tune how the caching works for your Crowd application, please see  5.2 Configuring Caching for an Application

To enable caching on the Crowd server,

  1. Login to the Crowd Administration Console.
  2. Click the 'Options' link in the top navigation bar.
  3. Click the 'Caching' tab.
  4. Select the 'Enable' check-box, then click the 'Update' button.

Screenshot: 'Caching' 

Related Topics  


Crowd Documentation  



Document generated by Confluence on Jun 20, 2007 20:58