RFC 8707: Resource Indicators for OAuth 2.0
In plain English — editorial summary, not part of the RFC
This document specifies an extension to the OAuth 2.0 Authorization Framework defining request parameters that enable a client to explicitly signal to an authorization server about the identity of the protected resource(s) to which it is requesting access.
Document record
- Document ID
- RFC8707
- Published
- February 2020
- Authors
- B. Campbell; J. Bradley; H. Tschofenig
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9068JSON Web Token (JWT) Profile for OAuth 2.0 Access TokensCurrent
October 2021
- RFC 8705OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access TokensCurrent
February 2020
- RFC 8693OAuth 2.0 Token ExchangeCurrent
January 2020
- RFC 8628OAuth 2.0 Device Authorization GrantCurrent
August 2019
- RFC 8473Token Binding over HTTPCurrent
October 2018
- RFC 8414OAuth 2.0 Authorization Server MetadataCurrent
June 2018
- RFC 8392CBOR Web Token (CWT)Current
May 2018
- RFC 9101The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR)Current
August 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?