SELECT * from migration_model WHERE version = '999.0.0';Open Source Identity and Access Management For Modern Applications and Services
Before upgrading refer to the migration guide for a complete list of changes.
ldapldapidentity-brokeringadmin/apiadapter/javascriptoperatorBefore upgrading refer to the migration guide for a complete list of changes.
authorization-servicesdocsdist/quarkuscoredocsdocsdist/quarkusaccount/uicoreauthenticationcoreadmin/uiimport-exportdocsadmin/apidist/quarkusinfinispanauthorization-servicescoreaccount/uiadmin/uiauthenticationtestsuiteauthorization-servicesdocsstoragedocsadmin/uidocscoreuser-profileadmin/uidist/quarkusdocslogin/uicicoredocsuser-profileaccount/uitranslationscoreoidcdocsoperatordist/quarkusauthenticationdocsstorageuser-profilestorageuser-profiledist/quarkusoperatorauthentication/webauthnDue to an issue in the release process when deploying Keycloak using the Operator it installed the nightly container
instead of 24.0.0.
As a quick fix to the issue, the 24.0.0 container was tagged with nightly, and the nightly releases was temporarily
disabled.
If you installed or upgraded to 24.0.0 using the Operator before 5pm CET yesterday the database may have been updated
with the wrong versions. To check if you are affected connect to your database and run the following SQL command:
SELECT * from migration_model WHERE version = '999.0.0';If the above returns a matching row you will need to take some actions, otherwise database migrations will not run for future releases. To resolve this run the following SQL command:
UPDATE migration_model SET version = '24.0.0' WHERE version = '999.0.0';Before upgrading refer to the migration guide for a complete list of changes.
Before upgrading refer to the migration guide for a complete list of changes.
storageadmin/uicildapadmin/apildapldapstoragecicilogin/uitestsuiteBefore upgrading refer to the migration guide for a complete list of changes.
A new health check endpoint available at /lb-check was added.
The execution is running in the event loop which means this check is responsive also in overloaded situations when Keycloak needs to handle many requests waiting in request queue.
This behavior is useful, for example, in multi-site deployment where we do not want to fail over to the other site under heavy load.
The endpoint is currently checking availability of the embedded and external Infinispan caches. Other checks may be added later.
This endpoint is not available by default.
To enable it, run Keycloak with feature multi-site.
Proceed to Enabling and disabling features guide for more details.
Before upgrading refer to the migration guide for a complete list of changes.
samlcoreoidcdist/quarkusadmin/uidocsaccount/uiuser-profileuser-profileoperator