Keycloak Authz Client 19.0.2 is not backward compatible with Keycloak 18 and earlier
See original GitHub issueDescribe the bug
Hi everyone, we are seeing a few reports in Quarkus, most recently captured in https://github.com/quarkusio/quarkus/discussions/28649#discussioncomment-3900729, suggesting that using quarkus-keycloak-authorization
depending on KC 19.0.2 libraries does not work if it is used against KC 18 or earlier.
Version
18
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
Run Keycloak Authz Client 19.0.2 against Keycloak 18
Anything else?
No response
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Keycloak Authz Client 19.0.2 is not backward compatible with ...
Open Source Identity and Access Management For Modern Applications and Services - Keycloak Authz Client 19.0.2 is not backward compatible ...
Read more >How do I use an older Keycloak client with Quarkus 2.13 ...
java - How do I use an older Keycloak client with Quarkus 2.13, Keycloak 19 client is not backwards compatible with v18 server...
Read more >Upgrading Guide - Keycloak
Upgrade the Keycloak server. The database will no longer be compatible with the old server after the upgrade.
Read more >[keycloak-user] Admin client backward compatibility issue (2.5
Previous message: [keycloak-user] Group user property for SAML client ... versions if there are changes that are not backward compatible.
Read more >Dev Services and UI for OpenID Connect (OIDC) - Quarkus
Quarkus introduces an experimental Dev Services For Keycloak feature which ... only if the authorization code grant does not work (for example, a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The user has confirmed it still does not work…
We are actually OK as KC 19.0.2/19.0.3 are not in the 2.13.x stream. Still would be of some concern for the upcoming 2.14.x but less so…