Restrictions when using the Redis session cache

Edit online

There are a number of restrictions which apply when you are running a WebSEAL environment that utilizes a remote Redis session cache.

  1. There is no support for the WebSEAL switch-user capability;
  2. When a WebSEAL server is restarted the inactivity timeout for any sessions which that server is referencing is reset. In this situation the inactivity timeout will be started again when the session is next referenced by a WebSEAL server. Alternatively, the lifetime timeout will ensure that the session still expires after a period of time;
  3. Verify Identity Access does not provide an administrative interface to manage sessions which are stored in the Redis server. Native Redis utilities, like the redis-cli, should instead be used to manage the session data stored in the Redis server;
  4. Support for Redis Clusters is not available;
  5. IBM does not supply or support the Redis Server itself. The server must be obtained and managed separately.