OAuth 2.0 DPoP for the Implicit Flow
draft-jones-oauth-dpop-implicit-00

Document Type Expired Internet-Draft (individual)
Authors Michael Jones  , Brian Campbell  , John Bradley 
Last updated 2020-09-10 (latest revision 2020-03-09)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-jones-oauth-dpop-implicit-00.txt

Abstract

This specification 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 tokens. This specification compliments and builds upon the mechanisms defined in draft-fett-oauth-dpop, in which access tokens are returned from the token endpoint. In particular, this specification extends the Demonstration of Proof-of-Possession at the Application Layer (DPoP) mechanisms to also be usable with the OAuth 2.0 implicit flow, in which access tokens are returned from the authorization endpoint.

Authors

Michael Jones (mbj@microsoft.com)
Brian Campbell (brian.d.campbell@gmail.com)
John Bradley (ve7jtb@ve7jtb.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)