Advanced Authentication patterns at the Edge
summary
Advocates moving authentication to a Kubernetes‑native API gateway to centralize and automate auth and security. Uses Solo.io’s Gloo Edge built on Envoy, configured as YAML, and supports OAuth, API keys, rate limits and an embedded WAF. Demo wires Keycloak, extract JWT email claim into headers and enforces authorization via Open Policy Agent with a rule allowing only emails ending in solo.io; a different test user is rejected, showing the pattern works end to end.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:18Introduction
- 1:46Ingress options
- 2:24Microservices
- 5:43Kubernetes Native API Gateway
- 7:24Using Kubernetes Native API Gateway to expose legacy services
- 8:16Security team visibility
- 9:10Glue Edge
- 10:02Envoy Proxy
- 11:53Filter chain
- 13:15Virtual service
- 14:24Demo
- 21:09GLUAGE Enterprise
- 22:54Questions
related talks
36mAdvanced Authentication patterns at the Edge
26mOne Auth Gateway to authenticate them all
26mSecuring the Gateway: A Deep Dive Into Envoy Gateway's Advanced Security Pol...
50mArchitectural Patterns for Spring Security You Wish Your Tech Lead Knew
01h 03mSingle Sign On with Keycloak: why and how
21mDon't Be Afraid to Operate Alone! The ABCs of Authentication Infrastructure Management
39mSecure Authorization for Agentic AI in Multi-Domain Environments
54mHow to secure your Spring apps with Keycloak