One payload, several signatures
04The general JSON serialization can associate several signatures with one payload.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 7.2.1 ↗
RFC 7515 · § 7.2.1EXAMPLE
3 / 3
03
Acceptance policy
Check the required signatures; there is no universal all-signers rule.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Each signature has its own protected header and optional unprotected header.
- Each signature has its own protected header and optional unprotected header.
- Signatures are computed separately.
- The application defines which signatures must validate for acceptance.
The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy