JSON Web Token (JWT)
Abbreviation: JWT
Pronunciation: JAY-sahn WEHB TOH-kun (JAY-DOUBLE-YOU-TEE)
Also known as: JSON Web Token, JWT
Definition
A JSON Web Token is a compact, URL-safe format for carrying signed or encrypted claims between software systems using a header, payload, and cryptographic protection. Secure use of JSON Web Token (JWT) keeps secrets outside client code and logs, applies least privilege, prevents replay where needed, monitors anomalies, and separates authentication from authorization.
Overview
Meaning and scope
A JSON Web Token is a compact, URL-safe format for carrying signed or encrypted claims between software systems using a header, payload, and cryptographic protection. Secure use of JSON Web Token (JWT) keeps secrets outside client code and logs, applies least privilege, prevents replay where needed, monitors anomalies, and separates authentication from authorization.
Mechanism and operation
A practical review of JSON Web Token (JWT) must account for the following: Authentication establishes who or what is acting; authorization determines what it may do. Risks include accepting unsigned tokens, algorithm confusion, weak keys, missing audience checks, excessive lifetime, replay, leaked payload data, and insecure key rotation. A JWT is a compact claims container that may be signed or encrypted; decoding its segments does not verify signature, issuer, audience, time claims, or authorization. A sender creates claims such as issuer, subject, audience, scope, and expiration, while the receiver validates the token with approved algorithms and current keys.
Practical payment example
A merchant API checks a JWT signature, issuer, audience and expiry before honoring a payout request; decoding readable token claims alone is not authentication.
Operational checks
The JSON Web Token (JWT) recovery process should restore access without bypassing the original identity and authorization controls. Applications should validate issuer, audience, expiration, not-before time, signature algorithm, key identifier, scope, and revocation or rotation policy and should minimize sensitive claims. JSON Web Token (JWT) can participate in either process, but it must not be treated as a private key, blockchain token balance, or proof of asset ownership.
Distinctions and limits
In the context of JSON Web Token (JWT), decoding a credential is not the same as validating it. JWT is a data format, not automatically an access token, ID token, session, encryption method, blockchain token, or proof that every included claim is trustworthy.
Related reading
Related definitions: Authentication, authorization.
Example
A merchant API checks a JWT signature, issuer, audience and expiry before honoring a payout request; decoding readable token claims alone is not authentication.
Comparison
In the context of JSON Web Token (JWT), decoding a credential is not the same as validating it. JWT is a data format, not automatically an access token, ID token, session, encryption method, blockchain token, or proof that every included claim is trustworthy.
Key Takeaway
JWT standardizes protected claims, but safe use requires strict algorithm, signature, issuer, audience, expiration, key-management, and privacy validation.
Sources
- JSON Web Token (RFC 7519) — IETF (2026-08-01)
- JSON Web Signature (RFC 7515) — IETF (2026-08-01)
- OpenID Connect Core 1.0 — OpenID Foundation (2026-08-01)