-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
AMQ 7.12.1.GA
-
None
-
False
-
None
-
False
-
-
-
After upgrading to the latest version of AMQ with Hawtio-Next, we are seeing users locked out of the console with Status Code: 429 errors. We initially thought it was due to failed authentication / expired tokens, but reverting to the old console code mitigates the issue. We are using Hawtio with SSO.
"status": 429,
"statusText": "Too Many Requests",
"httpVersion": "HTTP/1.1",
"headers": [
In the logs we also see:
2024-09-10 11:45:00,313 WARN [io.hawt.system.Authenticator] Login failed due to: org.keycloak.exceptions.TokenNotActiveException: Token is not active 2024-09-10 11:45:00,341 WARN [io.hawt.system.Authenticator] Login failed due to: org.keycloak.exceptions.TokenNotActiveException: Token is not active 2024-09-10 11:45:00,446 WARN [io.hawt.system.Authenticator] Login failed due to: org.keycloak.exceptions.TokenNotActiveException: Token is not active 2024-09-10 11:45:00,521 WARN [io.hawt.system.Authenticator] Login failed due to: org.keycloak.exceptions.TokenNotActiveException: Token is not active
Console usage has not changed and rolling back to the older hawtio-next version mitigates the issue (though it as the issue of header sizes being too large)
