Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Keycloak 18.0, OpenID Connect Logout, redirect_uri is no longer supported #674

Closed
PlusaN opened this issue May 25, 2022 · 4 comments
Closed
Assignees
Labels
🐛 Bug [ISSUE] Ticket describing something that isn't working 🕸️ Inactive

Comments

@PlusaN
Copy link

PlusaN commented May 25, 2022

Environment

Self-Hosted (Bare Metal)

Version

2.0.9

Describe the problem

Keycloak 18.0.0 release notes:

OpenID Connect Logout

Previous versions of Keycloak had supported automatic logout of the user and redirecting to the application by opening logout endpoint URL such as http(s)://example-host/auth/realms/my-realm-name/protocol/openid-connect/logout?redirect_uri=encodedRedirectUri. While that implementation was easy to use, it had potentially negative impact on performance and security. The new version has better support for logout based on the OpenID Connect RP-Initiated Logout specification. The parameter redirect_uri is no longer supported; also, in the new version, the user needs to confirm the logout. It is possible to omit the confirmation and do automatic redirect to the application when you include parameter post_logout_redirect_uri together with the parameter id_token_hint with the ID Token used for login.

https://www.keycloak.org/2022/04/keycloak-1800-released.html

Additional info

No response

Please tick the boxes

Keycloak is an open source identity and access management solution
@PlusaN PlusaN added the 🐛 Bug [ISSUE] Ticket describing something that isn't working label May 25, 2022
@PlusaN
Copy link
Author

PlusaN commented May 27, 2022

I upgrade keycloak-js to latest version (18.0.0), the problem is no more. But I'm not sure if everything works correctly with the updated package. Need testing :)
yarn upgrade keycloak-js

@liss-bot liss-bot added the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label May 27, 2022
@liss-bot
Copy link
Collaborator

This issue has gone 6 weeks without an update. To keep the ticket open, please indicate that it is still relevant in a comment below. Otherwise it will be closed in 5 working days.

@liss-bot liss-bot added ⚰️ Stale [ISSUE] [PR] No activity for over 1 month and removed 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending labels Jun 27, 2022
@liss-bot
Copy link
Collaborator

liss-bot commented Jul 2, 2022

This issue was automatically closed because it has been stalled for over 6 weeks with no activity.

@liss-bot liss-bot closed this as completed Jul 2, 2022
@liss-bot liss-bot removed the ⚰️ Stale [ISSUE] [PR] No activity for over 1 month label Jul 2, 2022
@Lissy93
Copy link
Owner

Lissy93 commented Jul 3, 2022

I forgot to update this ticket, but this was fixed in #663

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug [ISSUE] Ticket describing something that isn't working 🕸️ Inactive
Projects
None yet
Development

No branches or pull requests

3 participants