You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Keys are stored in Redis to generate tokens. They are read when each service starts. However, if TeraServer changes the keys, which might happen in test mode when we completely flush the DB and regenerate default values, then the services are not updated with the new keys and calls to API fail with wrong tokens.
To Reproduce
Steps to reproduce the behavior:
Launch TeraServer in test mode with --enable_tests=1
Launch other services in test mode
Call the /api/tests/database/reset API to flush an regenerate the default DB
Create a new participant and get its static token
Use the new token to call an endpoint on the service (will be generated with the wrong key from the new DB)
Expected behavior
Service must be aware of changes in redis keys and update them in ServiceAccessManager.
The text was updated successfully, but these errors were encountered:
Describe the bug
Keys are stored in Redis to generate tokens. They are read when each service starts. However, if TeraServer changes the keys, which might happen in test mode when we completely flush the DB and regenerate default values, then the services are not updated with the new keys and calls to API fail with wrong tokens.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Service must be aware of changes in redis keys and update them in ServiceAccessManager.
The text was updated successfully, but these errors were encountered: