Description

We want to support keycloak-client with all the already released Keycloak server versions. Do we also want to support keycloak-client with the future server versions? I think we should.

Right now, keycloak-client fails with the keycloak-server nightly due the issue keycloak/keycloak-client#94 .

I think keycloak-client should be forward compatible with future Keycloak server versions due to this scenario:

• Some customer uses for example Keycloak server 26.0.5 and keycloak-client 26.0.3, which are fully compatible with each other.

• There is a release of Keycloak server 26.1.0. Now customer upgrades to that. The current client 26.0.5 should still work against Keycloak server 26.1.0 (This is what does not work currently as when client calls GET, the returned JSON may contain unknown fields like bruteForceStrategy on realm).

• After few days, there is a release of keycloak-client 26.0.6 (which can contain the new properties added in keycloak server 26.1.0 like for example RealmRepresentation.bruteForceStrategy). The client should still work against Keycloak server 26.1.0 and now it is also able to support the new capabilities (like realm.bruteForceStrategy).

Possible solution

Make sure that admin-client is able to ignore properties, which are not known.

Discussion

No response

Motivation

No response

Details

No response