diff --git a/docs/release/trg-5/trg-5-07.md b/docs/release/trg-5/trg-5-07.md
index 0fb2db49db99..f503a5262cb9 100644
--- a/docs/release/trg-5/trg-5-07.md
+++ b/docs/release/trg-5/trg-5-07.md
@@ -4,6 +4,7 @@ title: TRG 5.07 - Chart Dependencies
 
 | Status | Created     | Post-History                                  |
 |--------|-------------|---------------------------------------------- |
+| Update | 31-Jul-2026 | Add Keycloak dependency alignment             |
 | Update | 28-Oct-2023 | Migrate from Bitnami to Cloudpirates          |
 | Update | 20-Sep-2023 | Adjust PostgreSQL version                     |
 | Active | 07-Mar-2023 |                                               |
@@ -11,7 +12,7 @@ title: TRG 5.07 - Chart Dependencies
 
 ## Why
 
-Dependencies like a database (postgresql) are used across Eclipse Tractus-X. It's critical to align those common dependencies when those dependencies are later replaced with hosted versions, like the database. Single instance of these dependencies that can be shared among all products in the future.
+Dependencies like a database (postgresql) or an identity provider (keycloak) are used across Eclipse Tractus-X. It's critical to align those common dependencies when those dependencies are later replaced with hosted versions, like the database. Single instance of these dependencies that can be shared among all products in the future.
 
 ## Description
 
@@ -52,3 +53,21 @@ The following table describes the required version of dependencies for all produ
 | Name     | Repo URL                                                         | Chart version | App version |
 |----------|------------------------------------------------------------------|:-------------:|:-----------:|
 | postgres | [Cloudpirates](https://registry-1.docker.io/cloudpirates)        |    0.11.x     |   18.x.x    |
+| keycloak | [Cloudpirates](https://registry-1.docker.io/cloudpirates)        |    0.13.x     |   26.x.x    |
+
+## Migrating from Bitnami to Cloudpirates
+
+The Bitnami catalog for the affected dependencies (e.g. PostgreSQL, Keycloak) is being deprecated, so products
+should migrate to the Cloudpirates charts referenced above. A generic migration guide and a concrete example
+are available to support this transition:
+
+- Generic guide: [GENERIC_BITNAMI_TO_CLOUDPIRATES_KEYCLOAK_MIGRATION_GUIDE.md](https://github.com/eclipse-tractusx/tutorial-resources/blob/main/migration-guides/GENERIC_BITNAMI_TO_CLOUDPIRATES_KEYCLOAK_MIGRATION_GUIDE.md)
+- Reference implementation (Industry Core Hub): [BITNAMI_TO_CLOUDPIRATES_KEYCLOAK_MIGRATION_GUIDE.md](https://github.com/eclipse-tractusx/industry-core-hub/blob/main/docs/migration-guides/BITNAMI_TO_CLOUDPIRATES_KEYCLOAK_MIGRATION_GUIDE.md)
+
+:::caution token format changes between Keycloak versions
+
+When upgrading Keycloak across several major versions (e.g. from 22.x to 26.x), be aware of changes in the
+issued token format. Verify that all clients and services consuming the tokens are compatible with the target
+version before rolling out the migration.
+
+:::