Redis Keys

Edit online

When a session is sent to the Redis server by WebSEAL up to 3 keys will be created in the Redis server to represent the session.

To help isolate the WebSEAL session data from any other data which might be stored in the Redis server each of the keys will be prefixed with a fixed string, as speecified by the 'key-prefix' configuration entry within the '[redis]' configuration stanza.

The following keys will be created by WebSEAL:
  1. The session data itself will be stored in a single Redis 'hash'. The key for the session data will be constructed from the configured Redis key prefix, the 'session-' string, and the session identifier. For example: 'isva-session-hroagteRa2VRpzaqsFNFovI29d…'
  2. The list of WebSEAL clients which have a local copy of the session will be stored in a Redis 'set'. The key for this set will be constructed from the configured Redis key prefix, the 'client-' string, and the name of the key which stores the corresponding session data. For example: 'isva-client-isva-session-hroagteRa2VRpzaqsFNFovI29d…'. This data is used to keep track of session inactivity across the cluster of WebSEAL servers.
  3. The count of concurrent sessions for a single user will be stored in a Redis 'set'. The key for this set will be constructed from the configured Redis key prefix, the 'user-' string, and the session identifier. For example: 'isva-user-hroagteRa2VRpzaqsFNFovI29d…'
The following figure is an example of the Redis keys which are created for a single user session:
isva-session-hroagteRa2VRpzaqs...
  {
    entry: value
    ...
  }
 
isva-client-isva-session-hroagteRa2VRpzaqs...
  [
    57d93b14-149c-4307-91d3-…,
    290887dd-7e40-4c80-be15-…,
    ...
  ]
 
isva-user-testuser
  [
    hroagteRa2VRpzaqs...,
    klj43kjl432jk...,
    ...
  ]