Authentication Cache Timeouts

Set a cache timeout value to cache user or administrator authentication credentials, which improves runtime performance.

Set timeout properties to avoid repeatedly reauthenticating users— a benefit of particular interest for device clients that receive separately authenticated messages. If a user logs in successfully, he or she can reauthenticate with the same credentials without validating them against a security repository. However, if the user provides a user name or password that is different from the ones cached, Unwired Server delegates the authentication request to the security repository.

This property affects only authentication results: Authorization results and failed authentication results are not cached.

For example, if an MBO is protected by "LogicalRoleA", and the security configuration that MBO is deployed in has a role mapping to "PhysicalRoleA", each time a user tries to access this MBO, the provider checks to see if they are in PhysicalRoleA based on cached role membership from the original authentication. It does not check the security repository each time thereafter.

By default, the cache timeout value is 3600 (seconds). This value is enabled whether the property exists or not. You can change this value by configuring a new value for the property in Sybase Control Center for the appropriate security configuration. Or, you can set the value to 0, to restrict access and force reauthentication.

Related tasks
Enabling Authentication Caching and Reducing Log Levels
Disabling Authentication Caching and Increasing Log Levels