Don't Be Afraid to Operate Alone! The ABCs of Authentication Infrastructure Management
summary
Giftee built a Keycloak-based authentication platform deployed in three stages: a Keycloak sandbox for new services, gradual migration of legacy apps, then broader adoption. They chose Keycloak over commercial IdPs to control costs, implemented passwordless authentication using Google OIDC with Google MFA and disabled password logins, and manage scope by storing only login attributes in Keycloak, using a master realm with delegated admin roles to distribute client configuration and reduce single-operator toil; the setup is documented for reuse.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:30Why Keycloak chosen
- 5:43Keycloak at Gifty
- 7:32Operating alone challenges
- 9:21Permission delegation
- 11:29Keycloak lessons learned
- 12:57Keycloak community power
- 14:04Q&A
- 15:37Multi-tenancy Q&A
- 17:58Docs improvements Q&A
- 18:59Attribute storage Q&A
related talks
46mBuilding a Unified Authentication Platform Using Keycloak
31mDelegate Authentication and a Lot More To Keycloak With OpenID...
35mAuthentication Challenges In Multi-Region Deployments
01h 12mIdentity 2.0: the what, why and how of social and federated login
01h 06mTutorial: Passkeys to the People: Building a Modern MFA Application with Open Source...
05mKeynote: Modernizing Railway IT Architecture: Secure-by-D...
01h 03mSingle Sign On with Keycloak: why and how
27mDesigning an Agentic AI-Ready Secure Authentication and Authorization Platform