User session storage backed by Redis.
This implementation uses core.redis as client and imposes the following requirements to him:
- {@link ConnectionType.SUBSCRIBER} connection needs to be established and available.
Key space notification events needs to be enabled on Redis Server side.
This is needed for receiving of key space notification events about refresh token keys deletion, expiration or eviction,
in order to remove them from list of active user sessions.
- {@link ConnectionType.REGULAR} connection needs to have detect_buffers option enabled, because it stores and reads
serialized user session metadata as {@link Buffer} instances.
- {@link RedisClientInstance.db} property should always return a valid db index.
It is recommended to not change db after {@link ConnectionType.REGULAR} connection was established.
User session storage backed by Redis.
This implementation uses core.redis as client and imposes the following requirements to him:
- {@link ConnectionType.SUBSCRIBER} connection needs to be established and available. Key space notification events needs to be enabled on Redis Server side. This is needed for receiving of key space notification events about refresh token keys deletion, expiration or eviction, in order to remove them from list of active user sessions.
- {@link ConnectionType.REGULAR} connection needs to have detect_buffers option enabled, because it stores and reads serialized user session metadata as {@link Buffer} instances.
- {@link RedisClientInstance.db} property should always return a valid db index. It is recommended to not change db after {@link ConnectionType.REGULAR} connection was established.