# Keycloak.X Update

DevFeed: [Keycloak.X Update](<https://devfeed.tech/articles/keycloak-x-update-31587.md>)

Original publisher: [Read original article](<https://www.keycloak.org/2021/10/keycloak-x-update>)

Author: Stian Thorgersen

Published: 2021-10-28T00:00:00Z

Content type: article

Language: en

Sources: [Keycloak Blog](<https://devfeed.tech/sources/keycloak-blog.md>)

Topics: [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [migration](<https://devfeed.tech/topics/migration.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>)

Tags: [cloud](<https://devfeed.tech/tags/cloud.md>), [idm](<https://devfeed.tech/tags/idm.md>), [kerberos](<https://devfeed.tech/tags/kerberos.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [ldap](<https://devfeed.tech/tags/ldap.md>), [migration](<https://devfeed.tech/tags/migration.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [saml](<https://devfeed.tech/tags/saml.md>), [sso](<https://devfeed.tech/tags/sso.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>)

## AI overview

A 2021 update on Keycloak.X outlines a planned move from WildFly to Quarkus, emphasizing improved user experience, simpler configuration, cloud-native deployment, and migration support for breaking changes.

## Source excerpt

It's been quite some time since we announced the plans around Keycloak.X, two years in fact. Due to other priorities we've been a bit distracted, but now it's finally full speed ahead. Keycloak.X will be lighter, faster, easier, more scalable, more cloud native, and a bunch of other things. Expect greatness coming your way! As part of Keycloak.X we're not only making code changes, but there will also be a cultural shift where the team behind Keycloak will focus a lot more on user experience and the delivery of a manageable solution over simply pieces of code. There will be some disruptive changes coming, but we will strive to make the transition as easy as possible for everyone. For breaking changes such as moving from WildFly to Quarkus we plan to provide 6 months to do the migration. If that is not enough there is Red Hat Single Sign-On, which is a supported build of Keycloak by Red Hat. Red Hat Single Sign-On 7, which is based on current Keycloak architecture, has support until June 2024 (currently says 2023, but will soon be extended to 2024). We will follow-up to this blog post with more details in the future, but for now let's look at some of the highlights coming to Keycloak.X. Highlights Experiences As mentioned previously a lot more attention will be put on your experience with Keycloak. With this in mind we have identified a few experiences that we believe cover a wide range of different use-cases: App developer Developers that are integrating Keycloak with applications and services Customizer Developers that are extending Keycloak or integrating with other systems Bridge Using Keycloak as a bridge between applications and other identity solutions Regular A typical small to medium-sized deployment of Keycloak Super-sized Elastic and highly available deployment of Keycloak for very large use-cases SaaS A extension to super-sized where Keycloak enables identities for SaaS, CIAM, and B2C scenarios Quarkus We're switching to Quarkus as the platform to build Ke