metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 7519: JSON Web Token (JWT)

Still current, but amended. Parts of this document are changed or extended by RFC 7797, RFC 8725. Read both.

In plain English — editorial summary, not part of the RFC

JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.

Document record

Document ID
RFC7519
Published
May 2015
Authors
M. Jones; J. Bradley; N. Sakimura
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
30
Also known as
—
Updated by:
RFC 7797, RFC 8725

Topics

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/7519-json-web-token-jwt