Keycloak Journey - Evolution of Business and Community
summary
Hitachi explains concrete Keycloak outcomes: implemented device authorization grant for constrained devices, added a per-client refresh-token option and faster session loading, and achieved a Java implementation with Financial-grade API certification. Work with customers produces features like dynamic client registration plus OAuth 2.0 server metadata and PKCE so mobile apps get a confidential client per install. Community contributions exceed about 5,500 items with roughly 600 PRs. Several customer cases integrate external directories and use Keycloak as a policy decision point for attribute- and role-based access control.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:27Keycloak vision
- 3:56Customers versus communities
- 5:22Community activities
- 7:29Customer case studies
- 12:53Access control solutions
- 13:34Summary
related talks
07mWelcome + Opening Remarks
31mHigh-level API Security
05mKeynote: Modernizing Railway IT Architecture: Secure-by-D...
33mAuthenticate and authorize users “your way” when they access your appl & platf
31mDelegate Authentication and a Lot More To Keycloak With OpenID...
12mWhat Is New and Coming for Managing Cloud Native Identities in…
40mA Walkthrough of Keycloak
09mNavigating the Identity Abyss in the AI‑Native Era