RFC 9449: OAuth 2.0 Demonstrating Proof of Possession (DPoP)
In plain English — editorial summary, not part of the RFC
This document describes a mechanism for sender-constraining OAuth 2.0 tokens via a proof-of-possession mechanism on the application level. This mechanism allows for the detection of replay attacks with access and refresh tokens.
Document record
- Document ID
- RFC9449
- Published
- September 2023
- Authors
- D. Fett; B. Campbell; J. Bradley; T. Lodderstedt; M. Jones; D. Waite
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 39
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9470OAuth 2.0 Step Up Authentication Challenge ProtocolCurrent
September 2023
- RFC 9396OAuth 2.0 Rich Authorization RequestsCurrent
May 2023
- RFC 9207OAuth 2.0 Authorization Server Issuer IdentificationCurrent
March 2022
- RFC 9126OAuth 2.0 Pushed Authorization RequestsCurrent
September 2021
- RFC 9901Selective Disclosure for JSON Web TokensCurrent
November 2025
- RFC 10027Best Current Practice for Security of Cross-Device FlowsCurrent
August 2026
- RFC 9464Internet Key Exchange Protocol Version 2 (IKEv2) Configuration for Encrypted DNSCurrent
November 2023
- RFC 9635Grant Negotiation and Authorization Protocol (GNAP)Current
October 2024
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?