RFC 7518: JSON Web Algorithms (JWA)
In plain English — editorial summary, not part of the RFC
This specification registers cryptographic algorithms and identifiers to be used with the JSON Web Signature (JWS), JSON Web Encryption (JWE), and JSON Web Key (JWK) specifications. It defines several IANA registries for these identifiers.
Document record
- Document ID
- RFC7518
- Published
- May 2015
- Authors
- M. Jones
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 69
- Also known as
- —
- Updated by:
- RFC 9864
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7519JSON Web Token (JWT)Updated
May 2015
- RFC 7517JSON Web Key (JWK)Current
May 2015
- RFC 7516JSON Web Encryption (JWE)Current
May 2015
- RFC 7520Examples of Protecting Content Using JSON Object Signing and Encryption (JOSE)Current
May 2015
- RFC 7521Assertion Framework for OAuth 2.0 Client Authentication and Authorization GrantsCurrent
May 2015
- RFC 7515JSON Web Signature (JWS)Current
May 2015
- RFC 7522Security Assertion Markup Language (SAML) 2.0 Profile for OAuth 2.0 Client Authentication and Authorization GrantsCurrent
May 2015
- RFC 7523JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization GrantsCurrent
May 2015
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?