RFC 9597: CBOR Web Token (CWT) Claims in COSE Headers
In plain English — editorial summary, not part of the RFC
This document describes how to include CBOR Web Token (CWT) claims in the header parameters of any CBOR Object Signing and Encryption (COSE) structure. This functionality helps to facilitate applications that wish to make use of CWT claims in encrypted COSE structures and/or COSE structures featuring detached signatures, while having some of those claims be available before decryption and/or without inspecting the detached payload. Another use case is using CWT claims with payloads that are not CWT Claims Sets, including payloads that are not CBOR at all.
Document record
- Document ID
- RFC9597
- Published
- June 2024
- Authors
- T. Looker; M.B. Jones
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9964ML-DSA for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE)Current
May 2026
- RFC 9528Ephemeral Diffie-Hellman Over COSE (EDHOC)Current
March 2024
- RFC 9942CBOR Object Signing and Encryption (COSE) ReceiptsCurrent
June 2026
- RFC 9943An Architecture for Trustworthy and Transparent Digital Supply ChainsCurrent
June 2026
- RFC 9053CBOR Object Signing and Encryption (COSE): Initial AlgorithmsUpdated
August 2022
- RFC 9052CBOR Object Signing and Encryption (COSE): Structures and ProcessUpdated
August 2022
- RFC 8725JSON Web Token Best Current PracticesCurrent
February 2020
- RFC 8392CBOR Web Token (CWT)Current
May 2018
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?