Hi Dhilip,
User Authorization Cache:
The User Authorization cache remembers unique Policy Authorization results by User Directory OID and user DN + filter path + filter class + resolution. It is not unique to sessions. The entries in the Authorization cache are determined by (number of users) * (number of policies for which user could be authorized). Entries live for the length of time specified by the Cache Entry Lifetime setting. User Authorizations that are cached may not match the entries in the Policy Store for up to the length of time that the Authorization cache is alive.
Resource Cache:
The Resource cache caches the results of IsProtected calls and is independent of session. Documents that fall under Ignore Extensions are not stored in cache. Cache entries are based upon the full URI (including query string), Agent name, and action. The cache stores the Realm OID, the protection type (Authentication Scheme), and a redirection URL for credentials. It is recommended that the size of the Resource cache be set to the number of unique URIs on the site + 10%. For highly dynamic sites (>60% dynamic URLs, including query string differences), limit the size of the cache or disable it altogether. It is best to set the timeout of the Resource cache to expire items before the cache fills completely.
User Session Cache:
The User Session cache caches Authentications and Authorizations. Authentication is based upon session ID and Realm OID and is dependent upon the number of Realms to which a user has access (e.g. 10 users accessing 100 Realms will fill a cache of size 1000). Authorization is based upon session ID and resource (Full URI, Method, and Agent name). Response information is cached by each process and stored with a timestamp denoting its validity. The maximum session time is also stored for cleanup of entries. Logout does not flush the cache.
Also refer the below links for more information
Understanding Policy Server and Web Agent Caches
What is the Webagent cache size and memory used?
How to control authorization cache at policy server?
Regards,
Leo Joseph