The following security cache custom properties determine whether the authentication cache is enabled or disabled. If the authentication cache is enabled, as recommended,
these custom properties specify the initial size of the primary and secondary hash table caches, which affect the frequency of rehashing and the distribution of the hash algorithms.
Important: The com.ibm.websphere.security.util.tokenCacheSize and com.ibm.websphere.security.util.LTPAValidationCacheSize properties were replaced with the com.ibm.websphere.security.util.authCacheSize property.
WebSphere Application Server includes the following security cache custom properties:
com.ibm.websphere.security.util.authCacheEnabled
Whether to disable the authentication cache. IBM recommends that you leave the authentication cache enabled for performance reasons. However,
you can disable the authentication cache for debug or measurement purposes.
Default:
True
com.ibm.websphere.security.util.authCacheSize
The initial size of the primary and secondary hash table caches.
A higher number of available hash values might decrease the occurrence of hash collisions. A hash collision results in a linear search for the hash bucket, which might decrease the retrieval time. If several entries compose a hash table cache, you create a table with a larger capacity that supports more efficient hash entries instead of allowing automatic rehashing determine the growth of the table. Rehashing causes every entry to move each time.