Several recipients, one ciphertext
04The general JSON representation can carry recipient-specific key material for one encrypted message.
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 7516 · § 7.2.1EXAMPLE
3 / 3
03
Open one envelope
A recipient recovers the CEK and checks the shared encrypted content.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Recipients can have different key-management parameters.
- Recipients can have different key-management parameters.
- They share the encrypted content.
- Each intended recipient must obtain the same CEK through its applicable key-management procedure.
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