OAuth 2.0 Token Revocation
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 11
- Abstract
- This document proposes an additional endpoint for OAuth authorization servers, which allows clients to notify the authorization server that a previously obtained refresh or access token is no longer needed. This allows the authorization server to clean up security credentials. A revocation request will invalidate the actual token and, if applicable, other tokens based on the same authorization grant.
- Publication Date
- 2013-08-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC7009- Link
- https://doi.org/10.17487/RFC7009
- Author(s)
- Torsten LodderstedtStefanie DroniaMarius Scurtescu
Latest version of IETF RFC 7009
Document Versions — IETF RFC 7009
-
▶ IETF RFC 7009 (2013-08-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 5226 [Superseded*]
- IETF RFC 5246 [Superseded*]
- IETF RFC 6749 [Active*]
Bibliographic Reference(s)
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7009.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7009, OAuth 2.0 Token Revocation. Available at https://doi.org/10.17487/RFC7009
Snippet:
IETF RFC 7009, OAuth 2.0 Token Revocation. Available at https://doi.org/10.17487/RFC7009
HTML (ISO 690 compliant)
Preview:
IETF RFC 7009, OAuth 2.0 Token Revocation. Available at https://doi.org/10.17487/RFC7009
Snippet:
<span class="citation"><cite>IETF RFC 7009</cite>, OAuth 2.0 Token Revocation. Available at <a href="https://doi.org/10.17487/RFC7009" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7009</a></span>
SMPTE's HTML Pub
Preview:
Snippet:
<li> <cite id="bib-rfc7009">IETF RFC 7009</cite>, OAuth 2.0 Token Revocation <span class="doi">10.17487/RFC7009</span> </li>
Referenced By
- IETF RFC 7662 [Active*]
- IETF RFC 8414 [Active*]
- IETF RFC 8705 [Active*]