Crowd 2.1 : Authorisation Caching
This page last changed on Dec 29, 2008 by smaddox.
Caching is used to store run-time authentication and authorisation rules, which can be expensive to calculate. This page describes the cache that can be configured on the Crowd server, to store users' authentication and per-application permissions for a specified period. For an overview of the other types of caching offered by Crowd, please refer to Overview of Caching. Caching of Users' Application Permissions on the Crowd Server — The Authorisation CacheCrowd can store users' authentication and per-application permissions in a local cache for a specified period after retrieving the information from the directory and application data. The cached data will answer the following questions:
You might call this the 'has access' cache, or the 'authorisation cache'. Recommended setting: Enabled. For performance reasons, we recommend that the cache be enabled on the Crowd server. This is the default setting. The effect of caching the data is that users will retain access to applications for a period after their username or permission has been removed, i.e. until the server-side cache expires. You should disable the cache only if you need immediate results when removing users or their permissions. To enable caching of user-to-application permissions on the Crowd server,
Screenshot: 'Caching'
RELATED TOPICS
![]() ![]() ![]() |
![]() |
Document generated by Confluence on Nov 30, 2010 23:53 |