[
https://issues.apache.org/jira/browse/CAMEL-23664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18118668#comment-18118668
]
Urmila Unni commented on CAMEL-23664:
-------------------------------------
Update after trying the bump locally:
keycloak-client-version is used for both the client libraries
(keycloak-admin-client, keycloak-authz-client) and keycloak-core. keycloak-core
follows the Keycloak server versioning, so no single version is current for
both (26.0.12 doesn't exist for keycloak-core, and 26.6.2 doesn't exist for the
client libraries).
So I've split the property:
* keycloak-client-version → 26.0.12 (keycloak-admin-client and
keycloak-authz-client, used by camel-keycloak, camel-oauth and test-infra)
* new keycloak-version → 26.7.4 for keycloak-core (latest, and matches the
26.7 server image used by the integration tests)
The client libraries don't depend on keycloak-core, so there's no version
overlap. Build and camel-keycloak unit tests (130) pass locally.
> camel-keycloak: Upgrade to latest Keycloak 26.x version
> -------------------------------------------------------
>
> Key: CAMEL-23664
> URL: https://issues.apache.org/jira/browse/CAMEL-23664
> Project: Camel
> Issue Type: Dependency upgrade
> Components: camel-keycloak
> Reporter: James Netherton
> Priority: Minor
>
> Camel currently aligns with Keycloak 26.0.8 which was released Jan 13, 2025.
> At the time of writing, the latest version is 26.6.2 released May 20, 2026.
> If possible, it'd be good to upgrade to the latest release and not drift too
> far from what other frameworks align to.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
