Skip to main content

OAuth 2.0 Proof-of-Possession: Authorization Server to Client Key Distribution

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors John Bradley , Phil Hunt , Michael B. Jones , Hannes Tschofenig
Last updated 2015-10-14 (Latest revision 2014-06-26)
Replaced by draft-ietf-oauth-pop-key-distribution
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-oauth-pop-key-distribution
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Kathleen Moriarty
Send notices to

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


RFC 6750 specified the bearer token concept for securing access to protected resources. Bearer tokens need to be protected in transit as well as at rest. When a client requests access to a protected resource it hands-over the bearer token to the resource server. The OAuth 2.0 Proof-of-Possession security concept extends bearer token security and requires the client to demonstrate possession of a key when accessing a protected resource. This document describes how the client obtains this keying material from the authorization server.


John Bradley
Phil Hunt
Michael B. Jones
Hannes Tschofenig

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