OAuth 2.0 Demonstration of Proof-of-Possession at the Application Layer (DPoP)
draft-fett-oauth-dpop-04
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Daniel Fett , Brian Campbell , John Bradley , Torsten Lodderstedt , Michael B. Jones , David Waite | ||
| Last updated | 2020-03-04 | ||
| Replaced by | draft-ietf-oauth-dpop | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-oauth-dpop | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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.
Authors
Daniel Fett
Brian Campbell
John Bradley
Torsten Lodderstedt
Michael B. Jones
David Waite
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)