Validate JWTs from Multiple Issuers in kgateway
The article explains how kgateway enables validation of JSON Web Tokens (JWTs) from multiple identity providers within a Kubernetes environment. It outlines the structure and verification process of JWTs, emphasizing support for multiple issuers like Auth0 and Google. The guide demonstrates configuring a single policy to validate tokens, enforce audience restrictions, and forward user claims to upstream services.
- ▪kgateway's JWTPolicy resource allows multiple JWT issuers to be defined in one policy.
- ▪Each identity provider has a unique JWKS endpoint for public key distribution used in signature verification.
- ▪The solution validates tokens locally in the Envoy data plane without calling back the identity provider on each request.
- ▪Tokens are verified based on the 'iss' (issuer) claim to match the correct public key set.
- ▪Custom claims like 'sub' and 'email' can be forwarded as headers to upstream services.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/emmsddev/validate-jwts-from-multiple-issuers-in-kgateway-561f |
| Publication time | Sun, 17 May 2026 07:52:37 +0000 |
| Retrieval time | 2026-05-17T08:03:59.095Z |
| Last seen | 2026-05-17T08:03:59.095Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | -nGvYbLtdv6B |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3618182) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Emmanuel Chukwudi Posted on May 17 Validate JWTs from Multiple Issuers in kgateway #kgateway #jwt #kubernetes #security Production APIs often need to accept tokens from more than one identity provider for example, a tenant's own Auth0 tenant and Google Workspace for internal tools. kgateway's JWTPolicy resource lets you declare multiple issuers in one policy and attach it to any HTTPRoute, so you don't need a separate gateway per IdP.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
