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
{{ message }}
Repository navigation
Backwards compatibility of Keycloak API on major release?
#37457
We use the admin client to update and create realms. We also rely on the client for product deployment.
When there is a major Keycloak release, we first update our software that uses the client, and then update the Keycloak instance itself.
However, it seems that each major version of Keycloak is not backwards compatible, which leads to a blocked status.
Currently, we handle this by registering Jackson mixins to filter out changes if the connected instance is of the old major version. This approach seems very hacky and might not work at some point.
I assume it was a decision to not support backwards compatibility. Can someone provide a pointer to that decision for better comprehension?
Is there a more graceful way to handle backwards compatibility?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We use the admin client to update and create realms. We also rely on the client for product deployment.
When there is a major Keycloak release, we first update our software that uses the client, and then update the Keycloak instance itself.
However, it seems that each major version of Keycloak is not backwards compatible, which leads to a blocked status.
Currently, we handle this by registering Jackson mixins to filter out changes if the connected instance is of the old major version. This approach seems very hacky and might not work at some point.
All reactions