claim
One statement inside a token, as a name and value, such as sub (subject), exp (expiry), iss (issuer), aud (audience) or scope.
In more detail
Claims are only trustworthy after the signature has been verified, and even then they are inputs to a policy, not permission by themselves. Registered claim names such as iss, sub, aud and exp are defined by the JSON Web Token standard, and services can add their own.
Examples
{"sub":"alice","iss":"course","aud":"tasks","exp":4102444800,"scope":"tasks:read"}{ "sub": "usr_99", "role": "admin", "exp": 1767225600 }Related terms
- JSON Web Token — A compact signed token made of three base64url parts separated by dots: a header, a payload of claims and a signature.
- issuer — The party that created and signed a token, named in its iss claim.
- audience — The recipient a token is meant for, named in its aud claim, such as one particular API.
- subject claim — The sub claim in a token, which identifies the user or service the token is about.
- token expiry — The time after which a token must no longer be accepted, carried in a JSON Web Token as the exp claim.
- audience claim — The token claim naming who the token is meant for, so a service can refuse tokens minted for somebody else.
- issuer claim — The token claim naming who minted the token, for GitHub always https://token.actions.githubusercontent.com.
- trust policy — A JSON document on a cloud role that says who may assume the role and under which conditions.
- ClaimsPrincipal — The .NET object representing the current user, holding one or more identities and their claims.
- policy-based authorization — Protecting endpoints with named policies that bundle requirements, such as a scope claim and a role.
- scope claim — A token claim listing the permissions a client was granted, such as catalog.write.
- ID token — The signed token in OpenID Connect that tells a client who the user is and how they authenticated, meant for the client rather than for APIs.
- digital signature — A value computed from data and a secret key that lets anyone with the matching verification key confirm the data came from the key holder and was not changed.
Taught in
- JSON Web Tokens — Modern API Architecture: REST, GraphQL & gRPC
- OAuth Two And OpenID Connect — Modern API Architecture: REST, GraphQL & gRPC
- RBAC Contrasted With ABAC — Modern API Architecture: REST, GraphQL & gRPC
- Keyless Authentication: OIDC to the Cloud — Continuous Integration & Continuous Delivery Pipelines
- Security Landing Zones & Centralized Egress Inspection — Cloud Security & DevSecOps Engineering
- Workload Identity Federation: Eliminating Static Keys — Cloud Security & DevSecOps Engineering
- Zero-Trust Network Access & IdP Federation — Cloud Security & DevSecOps Engineering
- Authentication: JWTs and Claims — Modern .NET Core, C# & Enterprise Microservices
- Role-Based and Policy-Based Authorization — Modern .NET Core, C# & Enterprise Microservices
- OAuth2 & OpenID Connect: Social Auth & PKCE Flows — Production Full-Stack Engineering
- JWT Verification: Asymmetric Keys & Refresh Rotation — Production Full-Stack Engineering
- Multi-Tenant Identity: Tenant Isolation & Middleware — Production Full-Stack Engineering
- Authentication Versus Authorisation — Application Security & Threat Modeling for Engineers
- Workload Identity — Application Security & Threat Modeling for Engineers