When I start the test with a new user, a new key is created in redis successfully. However, whenever I refresh the page, while using the same user, a new key is stored in redis rather than using an already existing key.
Using sticky session in place of redis works, but it's not a desirable solution.
Concerto Platform version
5.0.27
Expected behavior
The session should be resumed if it's already present in redis
Actual behavior
A new key is being created in redis and the previous session is not being used
Steps to reproduce the issue
Using the environment variables to start using redis instead of the filesystem, configure the host, port and password, and creating a redis instance, then start a test that uses session.
Hello, I've been trying to use redis with the concerto platform by changing the following variables (right now I'm using k8s to host redis):
CONCERTO_SESSION_STORAGE: redis REDIS_HOST: host REDIS_PORT: 6379 REDIS_PASS: ''
When I start the test with a new user, a new key is created in redis successfully. However, whenever I refresh the page, while using the same user, a new key is stored in redis rather than using an already existing key.
Using sticky session in place of redis works, but it's not a desirable solution.
Concerto Platform version
5.0.27
Expected behavior
The session should be resumed if it's already present in redis
Actual behavior
A new key is being created in redis and the previous session is not being used
Steps to reproduce the issue
Using the environment variables to start using redis instead of the filesystem, configure the host, port and password, and creating a redis instance, then start a test that uses session.