<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/your-gateway-checked-the-jwt-that-is-not-authorization--9henhlmwy" -->

---
title: Your gateway checked the JWT. That is not authorization.
description: Validating a JWT at an API gateway only confirms identity, not permission. A common security gap arises when APIs trust the JWT subject but skip checking...
canonical: https://daily.dev/posts/your-gateway-checked-the-jwt-that-is-not-authorization--9henhlmwy
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Your gateway checked the JWT. That is not authorization. | daily.dev
og:description: Validating a JWT at an API gateway only confirms identity, not permission. A common security gap arises when APIs trust the JWT subject but skip checking...
og:url: https://daily.dev/posts/your-gateway-checked-the-jwt-that-is-not-authorization--9henhlmwy
og:image: https://api.daily.dev/og/posts/9HENHlmwy.png
og:image:alt: Your gateway checked the JWT. That is not authorization.
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Your gateway checked the JWT. That is not authorization.

**[Auth By Example](https://daily.dev/sources/7eadcwhmohx0bchehapmt)** · [@authbyexample](https://daily.dev/authbyexample) · 1 min read · 0 upvotes · 0 comments

## Summary

Validating a JWT at an API gateway only confirms identity, not permission. A common security gap arises when APIs trust the JWT subject but skip checking whether that subject actually owns or may act on a client-supplied resource id. The piece argues authorization checks (subject, action, resource, tenant) must live next to the sensitive operation itself, evaluated against a policy the application cannot bypass by routing around it, rather than relying solely on gateway-level authentication.

## Content

Validating a token at the edge proves who called you. It does not answer whether that caller may delete invoice #4821, read another tenant’s row, or invoke an admin RPC.

Keep authentication at the gateway if you want. Put authorization next to the sensitive operation: subject, action, resource, and tenant (or other attributes) evaluated against a policy the app cannot skip by taking a different route.

A common failure mode: the API trusts `sub` from the JWT and then uses a client-supplied resource id with no ownership or relationship check. Edge authn passed; the business rule never ran.

Teach the split: authn = who; authz = what they may do to which thing, right now.

#security #authorization #backend #webdev

## Similar posts on daily.dev

- [OAuth and OIDC Beyond the Login Button: Identity as the API Security Control Plane](https://daily.dev/posts/oauth-and-oidc-beyond-the-login-button-identity-as-the-api-security-control-plane-bnyisfbqb) · Nordic APIs · 7 upvotes · 2 comments
- [Beyond Prompt Injection: The Non-Human Authorization Gap in Enterprise AI](https://daily.dev/posts/beyond-prompt-injection-the-non-human-authorization-gap-in-enterprise-ai-kyg9zgkps) · DEV · 2 upvotes · 0 comments
- [JWTs for AI Agents: Authenticating Non-Human Identities](https://daily.dev/posts/jwts-for-ai-agents-authenticating-non-human-identities-63fw1b4g5) · Security Boulevard · 0 upvotes · 0 comments
- [JWT Authentication Without the Confusion](https://daily.dev/posts/jwt-authentication-without-the-confusion-tvh5u1id9) · Medium · 1 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#authentication](https://daily.dev/tags/authentication), [#authorization](https://daily.dev/tags/authorization), [#api-gateway](https://daily.dev/tags/api-gateway), [#jwt](https://daily.dev/tags/jwt)

[View this post on daily.dev](https://daily.dev/posts/your-gateway-checked-the-jwt-that-is-not-authorization--9henhlmwy)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"DiscussionForumPosting","mainEntityOfPage":"https://daily.dev/posts/your-gateway-checked-the-jwt-that-is-not-authorization--9henhlmwy","headline":"Your gateway checked the JWT. That is not authorization.","text":"Validating a JWT at an API gateway only confirms identity, not permission. A common security gap arises when APIs trust the JWT subject but skip checking whether that subject actually owns or may act on a client-supplied resource id. The piece argues authorization checks (subject, action, resource, tenant) must live next to the sensitive operation itself, evaluated against a policy the application cannot bypass by routing around it, rather than relying solely on gateway-level authentication.","url":"https://daily.dev/posts/your-gateway-checked-the-jwt-that-is-not-authorization--9henhlmwy","datePublished":"2026-09-18T14:58:08.291Z","dateModified":"2026-09-18T14:58:24.848Z","author":{"@type":"Person","name":"Auth By Example","url":"https://daily.dev/authbyexample","image":"https://media.daily.dev/image/upload/s--Fgz7IgGQ--/f_auto/v1789653205/avatars/avatar_7EADCwHmOHX0bChEhAPmt?_a=BAMAMicg0","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":60}},"interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"isPartOf":{"@type":"WebPage","url":"https://daily.dev/sources/7eadcwhmohx0bchehapmt","name":"Auth By Example"}}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Auth By Example","item":"https://daily.dev/sources/7eadcwhmohx0bchehapmt"},{"@type":"ListItem","position":3,"name":"Your gateway checked the JWT. That is not authorization."}]}
```

