Scaling Identity for Global SASE with Keycloak
summary
Proposal: deploy autonomous Keycloak clusters as regional hub model (Americas, EMEA, APAC) to cut 200–300 ms cross‑region authentication delays, improve availability, and meet data‑sovereignty rules. Implementation uses the Keycloak operator, GitOps for config, canary upgrades, and Infinispan for cross‑cluster token caching and token‑exchange. A practical pilot is two region Keycloak deployment to measure latency and failover; automation and observability validate that hubs handle local auth traffic and keep global policies synchronized.
AI-written summary · about
chapters (7)
- 0:00Introduction and Speaker Background
- 0:48Understanding the Challenges of Identity in SASE
- 3:33Exploring the Regional Hub Model
- 4:53Why Keycloak is the Ideal Solution
- 5:41Designing a Regional Hub Architecture
- 7:56Implementing Automation and Overcoming Challenges
- 9:32Conclusion and Next Steps
related talks
35mAuthentication Challenges In Multi-Region Deployments
46mHighly available Identity and Access Management with multi-site Keycloak deployments in t...
26mWeb Scale SSO
21mDon't Be Afraid to Operate Alone! The ABCs of Authentication Infrastructure Management
12mWhat Is New and Coming for Managing Cloud Native Identities in…
06mStandardizing Authentication Flows in Keycloak Environments – Efficient Authorization S...
01h 03mSingle Sign On with Keycloak: why and how
39mSecure Authorization for Agentic AI in Multi-Domain Environments