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

The code remembers its challenge

03

The authorization server associates the challenge and method with the code it issues.

Related RFCs and changes

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

DIAGRAM§ 4.4 ↗
RFC 7636 · § 4.4EXAMPLE
3 / 3
The code remembers its challengeThe authorization server associates the challenge and method with the code it issues. Current state: Token request.The code remembers its challengechallenge + S256Authorization servercode C↳ challenge H↳ method S256bindcode C + verifiertoken endpoint
03
Token request

Present the code together with the original verifier.

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

The challenge is not an access token.

  • The challenge is not an access token.
  • The code is bound to the request’s challenge and method.
  • The client later sends the verifier to the token endpoint.
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. Create a transaction secret
  2. Derive the S256 challenge
  3. The code remembers its challenge
  4. A stolen code fails the proof
  5. Do not downgrade the method
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗