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
In local Keycloak deployment, the access_token generated with https requests are invalid even if the response is 200 OK.
For example, https://keycloak.local/auth/realms/iff/protocol/openid-connect/token produces invaid access_token.
HTTPS must be disabled in Keycloak for local deployment if no additional valid CA is present. In this case, Clients must get an error if using HTTPS for token generation request.
All clients in local deplyoment must only use HTTP with keycloak, unless a valid CA cert is added to the cluster.
The text was updated successfully, but these errors were encountered:
abhijith-hr
changed the title
[Issue] Invalid token in local keycloak, generated with HTTPS requests
[Issue] Invalid HTTPS requests to local Keycloak
Jul 31, 2024
In local Keycloak deployment, the access_token generated with https requests are invalid even if the response is 200 OK.
For example, https://keycloak.local/auth/realms/iff/protocol/openid-connect/token produces invaid access_token.
HTTPS must be disabled in Keycloak for local deployment if no additional valid CA is present. In this case, Clients must get an error if using HTTPS for token generation request.
All clients in local deplyoment must only use HTTP with keycloak, unless a valid CA cert is added to the cluster.
The text was updated successfully, but these errors were encountered: