This page last changed on May 05, 2008 by smaddox.

Caching is used to store run-time authentication and authorisation rules, which can be expensive to calculate. We recommend that you turn caching off during development cycles, and enable caching for production use.

In Crowd, data 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 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.

The configuration option described below manages both types of caching.

To fine-tune how caching works for your Crowd-integrated applications, please see Configuring Caching for an Application.

To enable data caching,

  1. Log in to the Crowd Administration Console.
  2. Click the 'Administration' tab in the top navigation bar.
  3. The 'General Options' screen will appear. Put a tick in the 'Enable Data Caching' checkbox.
  4. Click the 'Update' button.

Screenshot: 'Caching'

RELATED TOPICS

Crowd Documentation


Document generated by Confluence on Aug 27, 2008 20:21