Repository navigation
Migration path from 23.x to 26.7.2 #52579
|
Hey there, At work we are using Keycloak 23.x and we are currently rebuilding our setup to migrate to Keycloak 26.7. I have looked around the docs and the migration guide at https://www.keycloak.org/docs/latest/upgrading/index.html, but I can't seem to find a safe migration path shorter than following each and every version successively, which IMHO seems a bit risky. Is there a shorter officially supported migration path? Would upgrading to the latest patch of the 23.x line, then moving to the latest patch of each successive minor version be a shorter, yet safer such path? Thanks in advance! |
Replies: 1 comment
|
You do not need to start every intermediate Keycloak version. A stopped, direct upgrade from 23.x to 26.7.x is the normal database-migration model, provided you review and satisfy all intervening migration note 8000 s. There are two relevant mechanisms in the current code/docs:
I would use this sequence:
For a large database, consider generating/reviewing the migration SQL with References: |
You do not need to start every intermediate Keycloak version. A stopped, direct upgrade from 23.x to 26.7.x is the normal database-migration model, provided you review and satisfy all intervening migration notes.
There are two relevant mechanisms in the current code/docs:
23.0.0,24.0.0,24.0.3,25.0.0,26.0.0,26.1.0, …,26.7.0) and executes every migration newer than the version stored in the database. You get the intermediate migrations without booting each intermediate distribution.I would use this sequence: