Spring naar content
Opinie artikel

Upgrading to Keycloak 22.0.5
To dependency hell and back

Keycloak, a widely recognized open-source identity and access management tool, offers a range of features like Single Sign-On, social logins, and user federation, making it a popular choice for securing web applications and APIs across various organizations.

A standout feature of Keycloak is its Java Admin Client, a powerful tool that allows developers to automate Keycloak management through Java programming. This client offers a comprehensive suite of APIs, enabling a variety of administrative tasks such as the creation and management of realms, users, roles, groups, and clients. In this interactive blog series, we’ll dive into the world of fully automated Keycloak configurations, utilizing Java code exclusively. This series caters to both Keycloak novices and seasoned developers, offering deep insights into configuring Keycloak using Java code, simplifying your workflow.

What we have seen so far:

It has been a while since the last post was published, and knowing Keycloak’s release cycle, we need to invest some effort into upgrading to the latest version of Keycloak (22.0.5 at time of writing) and also adapt our project setup to it.

With the release of Keycloak 22 one of the most notable changes under the hood is the use of Quarkus 3. With the configuration setup we have built over the past few blogs in this series, this change will come with a few problems for us, which is what this blog post will revolve around.

read more: