Use the updateSCClientCacheConfiguration command to enable or disable
distributed cache and to modify the amount of time after token expiration
when downstream calls are allowed to complete. Use the optional distributedCache
parameter to allow or disallow the sharing of tokens across the cluster. WebSphere
Application Server supports caching for the security context token in both
cluster and non-cluster environments. In a cluster environment, you can set
the security context token cache as distributed. If the security context token
cache is set to distributed, all servers in the cluster share information
about issued tokens.
Use the optional minutesInCacheAfterTimeout parameter
to set the amount of time, in minutes, that the token is renewable after it
expires. This parameter extends the token expiration time by a specific number
of minutes. For example, if you specify 30 minutes, the token remains in cache
for this amount of time and the token is renewed for a limited time so that
a downstream call can be completed within this time frame.
Use the optional
renewIntervalBeforeTimeoutMinutes parameter to set the amount of time, in
minutes, that a renewal request can be issued before token timeout occurs.
The parameter prevents the token from expiring for the specified number of
minutes when a transaction is in process.
The following command example
enables distributed cache and allows 100 minutes as the time after token expiration
when downstream calls are allowed to complete:
AdminTask.updateSCClientCacheCustomConfiguration('[-customProperties
"[[cancelActionRST http://schemas.xmlsoap.org/ws/2005/02/trust/RST/SCT/Cancel]]"]')