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
DTR @mgarciaLKS will take care of Cloud Pirated Keycloak update.
2026-01-30 (Office Hours)
As discussed in Office Hours, @mgarciaLKS and @shijinrajbosch to discuss in planned meeting. @stephanbcbauer to be the sparring partner. Meeting planner for 8.Feb.2026
Impact of the version update and migration.
2026-02-02 (Mikel)
Will execute the first migration guide in the industry core hub repo. Will create and standardized one later on in the tutorial resources.
update 13.02.2026 by @stephanbcbauer
There will be a mail with all the information after we discussed the data migration part. @MonikaJacobsen who is missing until we can sent out the mail?
Additional: A sig-release issue for postgre is already on the board. For keycloak its missing @ds-hzimmer , @MonikaJacobsen
Upgrade target version suggested in migration guide is 26.x (latest at the moment is 26.5.x)
Questions:
Okay to upgrade to 26.x ?
Expected issues to consider when following the approach outlined in the migration guide?
Portal IAM (CentralIdp, Sharedidp) currently using Bitnamilegacy keycloak:25.0.6-debian-12-r0 in last release and in version as deplyoed on INT. To be determined if this can be upgraded by Portal team.
DTR still on Bitnamilegacy keycloak:22.0.3-debian-11-r14 on INT, as e.g. currently used by PURIS. DTR Helm Chart also references old versions.
IRS: Has an old Keycloak reference in the "full-irs" chart, but according to feedback this was never used / is not a required component.
BPDM successfully tested the migration guide for their "chart-tests" chart dependencies for Keycloak CentralIDP and PostgreSQL, using the linked guides. The guides were very helpful according to feedback, but Nico noticed issues for deploying multiple instances of databases (see "Upgrade of Postgres" task on board Tractus-X Open Meetings (view))
DTR team contacted regarding updating the Keycloak used by their service with some open questions. Shared information regarding changes in token format between Keycloak versions 22.x and 26.x to consider.
10.04.2026
need the committer to own this. (not a blocker for release)
Finalize the recommended Keycloak version or tag to be used as part of the Bitnami to Cloud Pirates migration initiative.
Useful links :
Affected repos with Bitnami:
@mgarciaLKS will take care of Cloud Pirated Keycloak update.
2026-01-30 (Office Hours)
As discussed in Office Hours, @mgarciaLKS and @shijinrajbosch to discuss in planned meeting. @stephanbcbauer to be the sparring partner. Meeting planner for 8.Feb.2026
2026-02-02 (Mikel)
Will execute the first migration guide in the industry core hub repo. Will create and standardized one later on in the tutorial resources.
update 13.02.2026 by @stephanbcbauer
There will be a mail with all the information after we discussed the data migration part. @MonikaJacobsen who is missing until we can sent out the mail?
Additional: A sig-release issue for postgre is already on the board. For keycloak its missing @ds-hzimmer , @MonikaJacobsen
update 27.02.2026 by @MonikaJacobsen
2026-03-19 by @ds-hzimmer
Input:
Migration guide (generic) created by @mgarciaLKS as mentioned above: https://github.com/eclipse-tractusx/tutorial-resources/blob/keycloak-migration/migration-guides/GENERIC_BITNAMI_TO_CLOUDPIRATES_KEYCLOAK_MIGRATION_GUIDE.md
Specific example of how it was performed for Industry Core Hub: https://github.com/eclipse-tractusx/industry-core-hub/blob/feature/keycloak-bitnami-to-cloudpirates-migration/docs/migration-guides/BITNAMI_TO_CLOUDPIRATES_KEYCLOAK_MIGRATION_GUIDE.md
Upgrade target version suggested in migration guide is 26.x (latest at the moment is 26.5.x)
Questions:
10.04.2026 by @ds-hzimmer
10.04.2026
need the committer to own this. (not a blocker for release)
17.07.2026
2026-07-24
DTR still open. Consider adding keycloak to TRG 5.07 (Do we still need that)?
2026-07-31