Visual RFC.
ALL RFCs / RFC 8725
Read the RFC ↗
RFC 8725 / MECHANISMS

Bind issuer and audience

04

A valid signature must be tied to the expected issuer and intended recipient.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 3.8 ↗
RFC 8725 · § 3.8EXAMPLE
3 / 3
Bind issuer and audienceA valid signature must be tied to the expected issuer and intended recipient. Current state: Wrong recipient.Bind issuer and audienceiss: expected issueraud: service AService AService Bwrong audreject
03
Wrong recipient

Reject a token addressed to a different service.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Bind cryptographic keys to the issuer being validated.

  • Bind cryptographic keys to the issuer being validated.
  • Validate the subject in the application’s context.
  • Use and validate audience to stop a token crossing to an unintended recipient.
DETAILS

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
All chapters in this RFC
  1. Do not let alg choose the policy
  2. A password is a weak MAC key
  3. Nested tokens need every check
  4. Bind issuer and audience
  5. Different purposes need different rules
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗