OAuth 2.0 Proof-of-Possession: Authorization Server to Client Key Distribution
draft-ietf-oauth-pop-key-distribution-03
| Document | Type | Expired Internet-Draft (oauth WG) | |
|---|---|---|---|
| Authors | John Bradley , Phil Hunt , Michael Jones , Hannes Tschofenig | ||
| Last updated | 2017-08-28 (Latest revision 2017-02-24) | ||
| Replaces | draft-bradley-oauth-pop-key-distribution | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
xml
pdf
htmlized
pdfized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | Kepeng Li | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | "Kepeng Li" <kepeng.lkp@alibaba-inc.com> |
https://www.ietf.org/archive/id/draft-ietf-oauth-pop-key-distribution-03.txt
Abstract
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.
Authors
John Bradley
Phil Hunt
Michael Jones
Hannes Tschofenig
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)