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

Errors describe different failures

04

The server distinguishes malformed requests, invalid tokens, and insufficient privileges.

Related RFCs and changes

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

DIAGRAM§ 3.1 ↗
RFC 6750 · § 3.1EXAMPLE
3 / 3
Errors describe different failuresThe server distinguishes malformed requests, invalid tokens, and insufficient privileges. Current state: Client response.Errors describe different failures401invalid_token403insufficient_scopepermissionDifferent failures need different client actions
03
Client response

Refresh or request appropriate authorization as applicable; do not treat every failure as the same error.

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

invalid_request describes a malformed authentication request.

  • invalid_request describes a malformed authentication request.
  • invalid_token can describe expiry, revocation, or other invalidity and normally uses 401.
  • insufficient_scope normally uses 403 and can identify the required scope.
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. Possession is the credential
  2. Put it in the request header
  3. URLs leave extra copies
  4. Errors describe different failures
  5. Limit the damage of disclosure
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗