Global Security - cache timeout settings and implications.

[Niall McLoughlin]

All

Under Global Security, there is a cache timeout setting. I understand that this is the length of time an authenticated user's credentials are held in cache before being discarded.

However, my understanding is that the JVM has to have some custom properties ( com.ibm.websphere.security.util.authCacheSize for example ) defined in order for the security cache to be effective. Is this correct or are the two unreleated ? I currently have a cache timeout setting defined, but no JVM custom properties defined, so does that negate the cache timeout setting ?

Is there a way of seeing the size and number of entries in the cache ?

Thanks in advance.

[DSPS]

Like lots of other services within WebSphere, it's a hash table. I
can see that the default size is 50 entries in WebSphere 6.0.

You can alter the setting by updating the JVM custom properties,
adding the com.....authCacheSize as a property and giving it a numeric
value for the new setting.

Servers => Application Servers => Pick the JVM => Java and Process
Management => Process Definition => Java Virtual Machine => Custom
Properties.
Add a new name / value pair in there.

Hope that helps.

Pete Bennett
Distributed Systems Professional Services Ltd.

Post by Niall McLoughlin
All
Under Global Security, there is a cache timeout setting. I understand that this is the length of time an authenticated user's credentials are held in cache before being discarded.
However, my understanding is that the JVM has to have some custom properties  ( com.ibm.websphere.security.util.authCacheSize for example ) defined in order for the security cache to be effective. Is this correct or are the two unreleated ? I currently have a cache timeout setting defined, but no JVM custom properties defined, so does that negate the cache timeout setting ?
Is there a way of seeing the size and number of entries in the cache ?
Thanks in advance.