Keycloak Introduction and Demo
summary
Keycloak runs as a dev server on localhost:8180 with an admin user and realm exported to JSON, an app redirects to OpenID Connect and receives ID and access tokens; the demo adds a required birthdate user profile field (HTML5 date), discovers a 403 from the backend until the realm role user is assigned, then API calls succeed and the token contains the new claim. A new test framework based on JUnit 5 is available. Project stats: ~27,000 stars, ~28,000 commits, ~1,300 contributors, 100+ releases.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:49Keycloak features and protocols
- 5:27User management and auth
- 7:56Token customization and tools
- 9:01Deployment and clustering
- 10:25Testing and contributions
- 11:10Keycloak history and growth
- 13:38Future development
- 15:03Live demo setup
- 17:18Authentication flow and claims
- 18:45User profile attributes
- 20:54Role assignment and debugging
- 22:43Q&A
related talks
54mHow to secure your Spring Apps with Keycloak
54mIdentity Management to your Spring Boot applications
51mEasily secure and add Identity Management to your Spring(Boot) applications
07mWelcome + Opening Remarks
31mDelegate Authentication and a Lot More To Keycloak With OpenID...
40mA Walkthrough of Keycloak
33mAuthenticate and authorize users “your way” when they access your appl & platf
32mEasily secure and add Identity Management to your Spring Boot applications
