Join our Newsletter — 33% off our NHI Course

Does OIDC use claims where OAuth scopes should handle consent?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: OAuth 2.0 scopes ask for access categories, while OpenID Connect claims return concrete facts in tokens and UserInfo responses, according to WorkOS. Keeping that split intact makes consent, token design, and service-level authorization easier to govern.

Editorial analysis by NHI Mgmt Group, based on content published by WorkOS: “Scopes vs. claims: What they are, how they differ, and when to use each”.

Key questions

Q: Why do claims belong in tokens instead of being modelled as scopes?

A: Claims are factual assertions about a subject, such as email, role, audience, or expiry.

Q: How can security teams tell whether token design is becoming too complex?

A: A good signal is scope proliferation without a matching increase in meaningful access categories.

Q: How should security teams design OAuth scopes without creating consent confusion?

A: Treat scopes as broad permission categories that a user can understand and approve.

Practitioner guidance

  • Define stable scope boundaries Limit scopes to broad, user-understandable access categories such as email, profile, or a clearly named resource scope.
  • Map data needs to claims Place user identity facts, roles, tenant context, and application-specific attributes in claims rather than in new scopes.
  • Validate claims at each resource server Check issuer, audience, expiration, and any domain-specific claims in every service that consumes the token.

Bottom line: Scopes define what access is being requested, while claims describe the facts that come back after access is granted.

Glossary terms: Scope, Claim, Identity Token, Userinfo Endpoint

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 6 days ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Scopes and claims fail for different reasons, so governance should not collapse them into one control plane. Scopes are consent and access categories, while claims are identity and grant facts. When teams blur that line, they either over-expand consent boundaries or under-specify the assertions downstream services need. The result is not just messy token design, but weak authorisation logic that is harder to audit and explain.

A question worth separating out:

Q: What is the difference between validating a token at the gateway and validating it in a resource server?

A: Gateway checks can filter obvious bad tokens, but they do not replace service-level validation. Each resource server should verify the claims it depends on, including issuer, audience, expiry, and any application-specific attributes. That keeps authorisation decisions aligned with the service that actually enforces them.

👉 Read our full editorial: Scopes and claims in OAuth and OIDC: where each belongs



   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.