WebSEAL session cache configuration
WebSEAL maintains two separate session caches, one for authenticated users and the other for users who are in the process of authenticating. Once a user is authenticated, their session cache entry is moved from the unauthenticated session cache to the authenticated session cache.
The following sections describe configuration and use of WebSEAL session caches:
- Maximum session cache entries value
- Cache entry lifetime timeout value
- Set a client-specific session cache entry lifetime value
- Cache entry inactivity timeout value
- Concurrent session limits
We can configure WebSEAL to limit the number of concurrent requests for a single user session.- Session cache limitation
Parent topic: Session cache configuration
Related concepts