The results of Keycloak identity summit: Keycloak2024

Dzmitry Tsybulka, CEO of TYMIQ and Keycloak expert, joined KeyConf24, a key event for Keycloak IAM technology, held on September 19, 2024, in Vienna.

About the event

Supported by the "Keycloak - OAuth2 Special Interest Group," KeyConf24 attracted global IAM professionals eager for Keycloak’s latest innovations, including work on OpenID FAPI standards, adaptive authentication, declarative configuration, and Open Banking integrations. Speakers included Daniel Goldscheider of the OpenWallet Foundation, with additional insights from Red Hat, JPMorgan, and Hitachi representatives on securing and scaling Keycloak.
‍

Current state, development dynamics, and community of Keycloak

Keycloak, launched by Red Hat in 2014, has grown to become a leading open-source IAM solution with a strong, active community of developers and adopters. Over its decade-long evolution, Keycloak has transitioned from a simpler identity and access management system to a comprehensive tool known for its flexibility, customization capabilities, extensive integrations, and scalability. 

The community, which now exceeds tens of thousands of contributors and users globally, is a driving force in its continuous development, enhancing features like adaptive authentication, multi-tenancy, and compliance with standards like OpenID Connect and SAML 2.0.

As digital security and IAM needs expand, Keycloak’s development has accelerated, with frequent updates focused on optimizing performance and aligning with industry standards. The technology’s shift toward OpenID FAPI standards highlights its utility in highly regulated sectors, such as finance and healthcare, where stringent security and privacy controls are essential.

OpenID FAPI (Financial-grade API) standards are a set of security and privacy guidelines developed by the OpenID Foundation, primarily for securing APIs in highly sensitive environments like banking and financial services.

For Keycloack’s ongoing progress, community input remains an important aspect, especially in declarative configuration,  integrations for cloud-native environments, and compatibility with enterprise and SaaS infrastructures. 

In Keycloak, declarative configuration is a method for defining configuration settings through code or structured files, like JSON or YAML, rather than through the Keycloak admin console. This approach allows developers to specify Keycloak settings (such as realms, clients, roles, and policies) directly in configuration files, which can then be versioned, automated, and deployed consistently across environments.

Keycloack development with TYMIQ

At TYMIQ, we offer specialized Keycloak services to help you customize an IAM solution to security tasks of your organization. If you need guidance or lack Keycloak experience, our consulting package is the right solution. 

What’s inside the package? In a nutshell, we’ll introduce you to the Keycloak basics, explain its usage scenarios, and outline its advantages/disadvantages as an IAM solution. Plus, we’ll assist you in evaluating if Keycloak aligns with your current environment. 

Our engineers are ready to discuss your specific goals, challenges, and potential solutions. Reach out at contact.tymiq.com for a free, in-depth consultation.