liveBook · Manning

Claim

A claim is an assertion, allegation, or request concerning a fact, attribute, right, entitlement, or proposition that may be recognized or evaluated.

How 8 Manning books explain it

ASP.NET Core in Action, 3e

A claim is a statement about an authenticated subject, represented as a type and value, that can support authorization decisions.

How it is used
Uses claims to personalize applications and determine access to protected endpoints.
How deep it goes
Explains claim representation, Identity storage, registration and retrieval, and policy checks, extending the treatment to JWT claims.
Examples
Illustrates claims with a registration name, airport boarding-pass access, and JWT subject and audience fields.
What you can do after
Apply it via ASP.NET Core Identity and authorization policies to add, read, and require claims.

Read how ASP.NET Core in Action, 3e explains claim →

Secure APIs

A token claim is a named statement or attribute encoded in a security token, such as a user's role or permission.

How it is used
Carries identity, access, lifecycle, role, permission, and scope information through JWT payloads for authentication and authorization decisions.
How deep it goes
Explains claims from JWT payload meaning through registered and custom forms and request authorization, while deferring broader RBAC detail.
Examples
Uses registered JWT payloads, permissions arrays, admin endpoints, OIDC identity claims, and PyJWT validation examples.
What you can do after
Apply claims via PyJWT by validating tokens and checking roles, permissions, or scopes before protected API operations.

Read how Secure APIs explains claim →

Building Web APIs with ASP.NET Core

A claim is a statement about an authenticated user or principal, represented as typed identity data and optionally carrying a value.

How it is used
Carries authenticated-user information in JWTs for authorization checks on API requests.
How deep it goes
Works through name and role claim creation, then outlines a mobile-phone policy without implementing its required registration and login changes.
Examples
Uses a username claim, per-role claims, and a proposed policy requiring both Moderator and mobile-phone claims.
What you can do after
Apply it via ASP.NET Core Identity and authorization policies to place role claims in JWTs and specify claim requirements.

Read how Building Web APIs with ASP.NET Core explains claim →

Effective Platform Engineering

A claim is an assertion about an authenticated entity or its permissions conveyed as identity data or in a token.

How it is used
Conveys team membership in identity data so platform services can authorize access to team resources.
How deep it goes
Explains where a team-membership claim comes from and how it enters a JWT, without detailing claim-format internals.
Examples
Uses a GitHub-backed CLI device-authorization flow and an Auth0 configuration exercise to illustrate a team-list claim.
What you can do after
Operate/configure an IDP integration that places GitHub team membership in a verifiable token for platform access.

Read how Effective Platform Engineering explains claim →

Authorization in Action

A claim is a statement about an entity, such as an identity attribute, conveyed by an identity or authorization system.

How it is used
Uses claims to identify requesters, scope identities, and supply attributes for authorization decisions.
How deep it goes
Explains claim sources, verification, normalization, and policy evaluation, stopping short of defining a universal claim schema.
Examples
Uses OIDC tokens, employment credentials, employer and certification attributes, device posture signals, and tenant-scoped subject identifiers.
What you can do after
Apply claims by verifying their sources, mapping them to attributes, and evaluating them in authorization policies.

Read how Authorization in Action explains claim →

Spring Security in Action, Second Edition

A claim is a named assertion about a subject or other token property carried in a JSON Web Token.

How it is used
Carries application-specific values from an authorization server to a resource server for authentication and authorization decisions.
How deep it goes
Explains creation, JWT decoding, authentication conversion, and framework configuration, stopping short of detailed claim-setting business logic.
Examples
Uses a priority claim set to HIGH, decoded JWT JSON, a custom authentication class, and a /demo response.
What you can do after
Apply it via Spring Security to carry token data into authentication and use that data in authorization rules.

Read how Spring Security in Action, Second Edition explains claim →

Architecting Autonomous Agentic Systems

A claim is an asserted legal entitlement or allegation seeking recognition, enforcement, or relief.

How it is used
Uses claims as governed concepts for retrieval, applicability, evidential sufficiency, explanation, routing, and agent-authority decisions.
How deep it goes
Defines claims relationally and qualifies their context, but stops short of determining claims or replacing policy and professional judgment.
Examples
Uses contractual provisions, judgments, evidence types, obligations, and legal propositions as connected knowledge-graph assertions.
What you can do after
Evaluate claims as governed knowledge without confusing semantic representation with factual determination or action authorization.

Read how Architecting Autonomous Agentic Systems explains claim →

.NET in Action, Second Edition

A claim is a named assertion about a subject or token context represented as a property in a security token.

How it is used
Uses claims to identify token context and enforce authorization decisions in a protected web service.
How deep it goes
Defines JWT payload claims and demonstrates lookup in an authorization handler, stopping short of token issuance or validation internals.
Examples
Uses aud, iss, nbf, iat, exp, sub, and preferred_username, then reads preferred_username during custom authorization.
What you can do after
Apply claims via ASP.NET Core authorization handlers to restrict an operation to a matching authenticated identity.

Read how .NET in Action, Second Edition explains claim →

Also covered in

What to know first

Related concepts

Questions about claim

What is claim?

A claim is an assertion, allegation, or request concerning a fact, attribute, right, entitlement, or proposition that may be recognized or evaluated.

Which Manning books explain claim?

ASP.NET Core in Action, 3e, Secure APIs, Building Web APIs with ASP.NET Core, Effective Platform Engineering, Authorization in Action, Spring Security in Action, Second Edition, Architecting Autonomous Agentic Systems and .NET in Action, Second Edition.

What should I know before learning claim?

Manning books that teach claim usually introduce OAuth, authentication, authorization and JSON Web Token first.

What kinds of claim are there?

Kinds of claim include access claim and security claim.

What is claim part of?

Claim is part of JSON Web Token. A JSON Web Token is a compact, URL-safe format for representing claims as a JSON object that can be digitally signed, integrity-protected, or encrypted.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.