deps: update quay.io/keycloak/keycloak docker tag to v26

[eclipse-apoapsis-bot]

This PR contains the following updates:

Package	Update	Change
quay.io/keycloak/keycloak	major	24.0.5 -> 26.0.7

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[mmurto]

As discussed at some point in the past, Keycloak 25 included some support for organizations and this version 26 includes full support for them, so it would be great to upgrade sooner rather than later to allow for experimenting with them.

[mnonnenmacher]

The upgrade to Keycloak 25 did not work out of the box with Compose: #388
I assume it's the same here, someone would have to test it and apply the required fixes because unfortunately we do not have any automatic tests for Compose.
Probably finishing #237 would provide better compatibility with feature releases than our current approach to configure the realm.

[mmurto]

The upgrade to Keycloak 25 did not work out of the box with Compose: #388 I assume it's the same here, someone would have to test it and apply the required fixes because unfortunately we do not have any automatic tests for Compose. Probably finishing #237 would provide better compatibility with feature releases than our current approach to configure the realm.

I agree. Were there some blockers at Bosch for upgrading, or would it be feasible to use features from 26?

[mnonnenmacher]

The upgrade to Keycloak 25 did not work out of the box with Compose: #388 I assume it's the same here, someone would have to test it and apply the required fixes because unfortunately we do not have any automatic tests for Compose. Probably finishing #237 would provide better compatibility with feature releases than our current approach to configure the realm.

I agree. Were there some blockers at Bosch for upgrading, or would it be feasible to use features from 26?

We are using a managed service (and have to) which is currently running version 23. So no, using features from 26 is unfortunately not an option for us.

[sschuberth]

Were there some blockers at Bosch for upgrading

Ah, good question: I was reading this as "problems at Bosch", but could be that @mnonnenmacher was referring to the problems with Compose also back then.

[sschuberth]

We are using a managed service (and have to) which is currently running version 23.

Could you initiate a push for that service to upgrade to 26 in the foreseeable future?

[mnonnenmacher]

We are using a managed service (and have to) which is currently running version 23.

Could you initiate a push for that service to upgrade to 26 in the foreseeable future?

I would not bet on that. I don't know how you want to use the organizations feature, but if it requires any code changes, maybe this could be done in a backward compatible way?

[sschuberth]

We are using a managed service (and have to) which is currently running version 23.

Could you initiate a push for that service to upgrade to 26 in the foreseeable future?

I would not bet on that. I don't know how you want to use the organizations feature, but if it requires any code changes, maybe this could be done in a backward compatible way?

FYI, as explained here (sorry, German only) release 26 decouples server from client versioning. So going forward, we could hopefully upgrade the client on our end more or less independently of the server.