Repository navigation
Migrating to the latest version of keycloak from version 11.0.2 #36267
gerhardvr-finclude
started this conversation in
Archive
Replies: 4 comments
|
Going to answer my own question here in case it benefits someone else. In the end there was nothing to be concerned about. I made a copy of my existing Keycloak DB, point the latest version of Keycloak to it, and Bob's you uncle! Keyclaok simply upgrade my DB without any issues whatsoever. Al data preserverved. Damn impressive considering that I wend from v11 to v26. |
0 replies
|
I need help updating the keylock post on GitHub from version 11 to version 26. I followed your recommendation but I haven't been successful. Could you help me? Do you have any step-by-step instructions? |
0 replies
|
Hi,
Unfortunately, it has been quite some time since I did the upgrade and I do not have step by step instructions. I do remember that it turned out to be much easier than I anticipated. I did not have to export and re-import data. Keycloak managed to update the database for me. I did however have to migrate the DB to mySQL 8 first.
I did make damn sure that I had backups of my database before I attempted the upgrade.
Best regards
Gerhard van Rensburg
Chief Operating Officer
Financial Inclusion Technology
M +27 83 601 7970 | E ***@***.******@***.***%0d>
…________________________________
From: Diego Romero ***@***.***>
Sent: 03 September 2025 15:24
To: keycloak/keycloak ***@***.***>
Cc: gerhardvr-finclude ***@***.***>; Author ***@***.***>
Subject: Re: [keycloak/keycloak] Migrating to the latest version of keycloak from version 11.0.2 (Discussion #36267)
I need help updating the keylock post on GitHub from version 11 to version 26. I followed your recommendation but I haven't been successful. Could you help me? Do you have any step-by-step instructions?
—
Reply to this email directly, view it on GitHub<#36267 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASWJCTXNKFJNRXXXTVRNIS33Q3TZJAVCNFSM6AAAAACFQTQ7N6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMRZGY2DCNQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
--
https://www.finclude.net <https://www.finclude.net/> | e:
***@***.*** ***@***.***>
|
0 replies
|
Thanks |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We are going to bite the bullet and upgrade to the latest version. While it would be awesome if the migration of the DB is handled automatically, I’m not too hopeful because of the huge difference in versions.
My thinking is that I will need to simply start with a clean installation and then recreate my clients and users manually. While this will be a pain in the butt, I will do so if there is not other way BUT the problem I foresee is the Client secrets. It is imperative that the client secrets stays the same but it seems not to be possible in Keycloak to set the client Secret. How to overcome this?
All reactions