RFC 7515: JSON Web Signature (JWS)

JSON Web Signature (JWS) represents content secured with digital signatures or Message Authentication Codes (MACs) using JSON-based data structures.…

Read RFC 7515 on the RFC Editor

Outgoing relationships (17 related RFCs)

Normative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Normative reference — RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
Normative reference — RFC 5280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
Normative reference — RFC 3629: UTF-8, a transformation format of ISO 10646
Normative reference — RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
Normative reference — RFC 4648: The Base16, Base32, and Base64 Data Encodings
Normative reference — RFC 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
Normative reference — RFC 4949: Internet Security Glossary, Version 2
Normative reference — RFC 20: ASCII format for network interchange
Normative reference — RFC 6176: Prohibiting Secure Sockets Layer (SSL) Version 2.0
Informative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Informative reference — RFC 2104: HMAC: Keyed-Hashing for Message Authentication
Informative reference — RFC 4086: Randomness Requirements for Security
Informative reference — RFC 6838: Media Type Specifications and Registration Procedures
Informative reference — RFC 3447: Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1
Informative reference — RFC 4122: A Universally Unique IDentifier (UUID) URN Namespace
Informative reference — RFC 6211: Cryptographic Message Syntax (CMS) Algorithm Identifier Protection Attribute

Incoming relationships (39 related RFCs)

Normatively referenced by — RFC 7519: JSON Web Token (JWT)
Normatively referenced by — RFC 7517: JSON Web Key (JWK)
Normatively referenced by — RFC 7518: JSON Web Algorithms (JWA)
Normatively referenced by — RFC 7591: OAuth 2.0 Dynamic Client Registration Protocol
Normatively referenced by — RFC 8725: JSON Web Token Best Current Practices
Normatively referenced by — RFC 7638: JSON Web Key (JWK) Thumbprint
Normatively referenced by — RFC 9711: The Entity Attestation Token (EAT)
Normatively referenced by — RFC 9068: JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens
Normatively referenced by — RFC 9449: OAuth 2.0 Demonstrating Proof of Possession (DPoP)
Normatively referenced by — RFC 9635: Grant Negotiation and Authorization Protocol (GNAP)
Normatively referenced by — RFC 7797: JSON Web Signature (JWS) Unencoded Payload Option
Normatively referenced by — RFC 8935: Push-Based Security Event Token (SET) Delivery Using HTTP
Normatively referenced by — RFC 8936: Poll-Based Security Event Token (SET) Delivery Using HTTP
Normatively referenced by — RFC 9679: CBOR Object Signing and Encryption (COSE) Key Thumbprint
Normatively referenced by — RFC 7520: Examples of Protecting Content Using JSON Object Signing and Encryption (JOSE)
Normatively referenced by — RFC 8292: Voluntary Application Server Identification (VAPID) for Web Push
Normatively referenced by — RFC 8688: A Session Initiation Protocol (SIP) Response Code for Rejected Calls
Normatively referenced by — RFC 8812: CBOR Object Signing and Encryption (COSE) and JSON Object Signing and Encryption (JOSE) Registrations for Web Authentication (WebAuthn) Algorithms
Normatively referenced by — RFC 9321: Signature Validation Token
Normatively referenced by — RFC 9447: Automated Certificate Management Environment (ACME) Challenges Using an Authority Token
Normatively referenced by — RFC 9448: TNAuthList Profile of Automated Certificate Management Environment (ACME) Authority Token
Normatively referenced by — RFC 9701: JSON Web Token (JWT) Response for OAuth Token Introspection
Normatively referenced by — RFC 9728: OAuth 2.0 Protected Resource Metadata
Normatively referenced by — RFC 9770: Notification of Revoked Access Tokens in the Authentication and Authorization for Constrained Environments (ACE) Framework
Normatively referenced by — RFC 9901: Selective Disclosure for JSON Web Tokens
Normatively referenced by — RFC 9932: Mutually Authenticating TLS in the Context of Federations
Normatively referenced by — RFC 9964: ML-DSA for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE)
Normatively referenced by — RFC 9999: Remote ATtestation procedureS (RATS) Conceptual Message Wrapper (CMW)
Informatively referenced by — RFC 7951: JSON Encoding of Data Modeled with YANG
Informatively referenced by — RFC 8392: CBOR Web Token (CWT)
Informatively referenced by — RFC 8152: CBOR Object Signing and Encryption (COSE)
Informatively referenced by — RFC 9052: CBOR Object Signing and Encryption (COSE): Structures and Process
Informatively referenced by — RFC 8224: Authenticated Identity Management in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 8747: Proof-of-Possession Key Semantics for CBOR Web Tokens (CWTs)
Informatively referenced by — RFC 7635: Session Traversal Utilities for NAT (STUN) Extension for Third-Party Authorization
Informatively referenced by — RFC 9421: HTTP Message Signatures
Informatively referenced by — RFC 8322: Resource-Oriented Lightweight Information Exchange (ROLIE)
Informatively referenced by — RFC 8387: Practical Considerations and Implementation Experiences in Securing Smart Object Networks
Informatively referenced by — RFC 9493: Subject Identifiers for Security Event Tokens