Issue: Unrecognized field "bruteForceStrategy"`

[Writtscher]

Current Behavior

We have updated our keycloak to the latest version 26.0.5. Now our configuration job in our pipeline fails with:

jakarta.ws.rs.ProcessingException: com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "bruteForceStrategy"

We are using v6.1.5/keycloak-config-cli-25.0.1. When is it planned to release a new version that fixes that issue?

Expected Behavior

No jakarta.ws.rs.ProcessingException: com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "bruteForceStrategy" error.

Steps To Reproduce

No response

Environment

• Keycloak Version: [26.0.5]
• keycloak-config-cli Version: [6.1.5/keycloak-config-cli-25.0.1]
• Java Version: [21]

Anything else?

No response

[ma1uta]

Should be fixed with #1162.

[Writtscher]

Thank you @ma1uta

Do you have any idea when it is planned to be released?

[ma1uta]

Unfortunately, no.

[service-github-lifetrust]

We are also waiting for the new release. Who can give us an idea on when to expect the new jar?
Thanks

[patrickmichalina]

Awaiting the docker release myself

[ValentinLorand]

Waiting for the release, currently blocked in my Keycloak upgrade :)

[Writtscher]

@ValentinLorand You can use the edge version for now and move to the released version when it is released.

[ValentinLorand]

It works correctly by extracting the jar from the edge version of the docker image, thanks.

[kbelosevic]

What is the docker image or path of this edge version?

[service-github-lifetrust]

@kbelosevic here it is:
https://hub.docker.com/r/adorsys/keycloak-config-cli/tags

I just did the following:

docker run --rm -it --entrypoint bash adorsys/keycloak-config-cli:edge
Then just docker cp <container-name>:/app/keycloak-config-cli.jar /tmp

After that you will have the latest .jar in the /tmp directory.

I don't really understand what is blocking the official release though...

[rblaine95]

Looks like 6.2.0 has been tagged and it includes Keycloak 26.0.5

• https://github.com/adorsys/keycloak-config-cli/releases/tag/v6.2.0

• https://hub.docker.com/layers/adorsys/keycloak-config-cli/6.2.0-26.0.5/images/sha256-342fbd3d32a60c63fca6568667ba73dfeb12c7e54831493f6dd7940e6b713327?context=explore

[ErwanDL]

Still seeing this today with the image adorsys/keycloak-config-cli:6.2.1-26, against a 26.0.2 Keycloak instance:

Error message:

HTTP 400 Bad Request{"error":"Unrecognized field \"bruteForceStrategy\" (class org.keycloak.representations.idm.RealmRepresentation), no t marked as ignorable (143 known properties: \"userFederationMappers\", \"rememberMe\", \"duplicateEmailsAllowed\", \"adminEventsDetailsEnabled\", \"users\", \"clientOfflineSessionMaxLifespan\", \"webAuthnPolicyRequireResidentKey\", \"webAuthnPolicyPasswordlessAvoidSameAu thenticatorRegister\", \"components\", \"otpPolicyType\", \"accessCodeLifespanUserAction\", \"id\", \"webAuthnPolicyAttestationConveyancePreference\", \"enabledEventTypes\", \"applications\", \"webAuthnPolicyPasswordlessSignatureAlgorithms\", \"eventsListeners\", \"ssoSes sionMaxLifespanRememberMe\", \"defaultDefaultClientScopes\", \"webAuthnPolicyPasswordlessCreateTimeout\", \"clientOfflineSessionIdleTimeout\", \"notBefore\", \"publicKey\", \"smtpServer\", \"clientPolicies\", \"resetPasswordAllowed\", \"webAuthnPolicyAvoidSameAuthenticato rRegister\", \"accessTokenLifespanForImplicitFlow\", \"webAuthnPolicyPasswordlessUserVerificationRequirement\", \"clientScopes\", \"internationalizationEnabled\", \"defaultRole\", \"accessTokenLifespan\", \"passwordCredentialGrantAllowed\", \"federatedUsers\", \"applicati onScopeMappings\" [truncated]])\n at [Source: REDACTED (`StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION` disabled); line: 1, column: 1283] (through reference chain: org.keycloak.representations.idm.RealmRepresentation[\"bruteForceStrategy\"])"}

[tim-koehler]

@ErwanDL I had the same issue when using keycloak-config-cli-26.0.5 in combination with the keycloak-admin-client in version 26.0.0. Upgrading the keycloak-admin-client to 26.0.3 solved it for me.

[ErwanDL]

@tim-koehler I'm not sure how to upgrade keycloak-admin-client specifically but upgrading my entire Keycloak instance to 25.0.5 has solved this issue indeed, thank you. Getting some new errors (500s and 404s) when running keycloak-config-cli now, but hey it's still progress 🙂