Beyond routing 🚀 Spring Cloud Gateway with style
summary
Shows working code that validates JWT via Okta keys inside a per-route Spring Security filter, then injects claim "name" as X-Claim-Name header so legacy services need no OAuth changes. Demonstrates a ModifyResponseBody filter that rewrites JSON fields at the gateway, a custom Converter to parse key=value filter args, and using the actuator routes API to change routes at runtime. Notes performance and reactive non‑blocking pitfalls and that the demos run successfully.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 3:48How does it work
- 11:03Scenario explanation
- 12:54Token validation
- 16:00Token claim
- 18:03Authenticator
- 25:58Configuration
- 27:53Performance
- 28:28Example
- 30:00Custom Converter
- 31:03Key Value
- 31:45Modifying body response
- 33:43Applying changes
- 34:50Considerations
- 35:18Warning
- 35:59Global filters
- 39:18Questions
related talks
43mSpring Cloud Gateway: Resilience and Security
47mSpring Cloud Gateway: Resilience, Security, and Observability
43mIdentity crisis: bending Spring Security to your advanced use-cases
50mArchitectural Patterns for Spring Security You Wish Your Tech Lead Knew
01h 11mSpring Cloud Gateway - Spencer Gibb, Sree Tummidi
08mBella Bai and Chris Sterling at SpringOne 2020
46mImplementing Microservices Security Patterns & Protocols with Spring Security
01h 30mSecuring Microservices with Spring Cloud Security