Repository navigation
Replies: 1 comment 3 replies
|
I think that it is not possible. They describes the changes here https://www.keycloak.org/2022/04/keycloak-1800-released.html in detail and it seems that setting the "--spi-login-protocol-openid-connect-legacy-logout-redirect-uri=true" backwards compatibility option only enables the use of the old redirect_uri parameter but the id token stays as a requirement. |
|
If I am not mistaken starting with KC19 you can omit |
|
Thanks @sschu that works! |
|
not any more (v26.3.3) |
Uh oh!
There was an error while loading. Please reload this page.
I'm trying to integrate Keycloak behind Azure B2C (using an OIDC client) and while the login works great, the logout from B2C doesn't actually fully log out of Keycloak. When B2C makes the front channel logout request to Keycloak, it doesn't pass the id_token_hint and is technically getting that logout confirmation page but the user doesn't see that since it's hidden in an iframe. It doesn't seem that B2C supports adding the id_token_hint to federated single sign out requests either.
Is it possible to make passing the id_token_hint to Keycloak optional somehow?
All reactions