Is there an existing issue for this?
Current Behavior
Hello!
We are integrating Keycloak SSO with Coder and have encountered an issue where, upon access token expiration, refreshing the page triggers multiple parallel refresh token requests to Keycloak (typically between 2 to 5 requests). This behavior puts unnecessary load on our Keycloak server and could lead to rate limiting or performance degradation under high concurrency.
For test we set access token lifespan in 2 minutes
Relevant Log Output
Expected Behavior
Expected behavior is one refresh token request on expire access token
Steps to Reproduce
- Configure Coder with Keycloak SSO
- Login with Keycloak
- Wait until the access token expires
- Refresh the page in the browser.
- Check event user in selected realm in Keycloak as Keycloak admin
- We get a lot of async request from backend to Keycloak
Environment
Additional Context
No response
Is there an existing issue for this?
Current Behavior
Hello!
We are integrating Keycloak SSO with Coder and have encountered an issue where, upon access token expiration, refreshing the page triggers multiple parallel refresh token requests to Keycloak (typically between 2 to 5 requests). This behavior puts unnecessary load on our Keycloak server and could lead to rate limiting or performance degradation under high concurrency.
For test we set access token lifespan in 2 minutes
Relevant Log Output
Expected Behavior
Expected behavior is one refresh token request on expire access token
Steps to Reproduce
Environment
Additional Context
No response