OAuth 2.0 Token Binding
draft-ietf-oauth-token-binding-08
| Document | Type |
Expired Internet-Draft
(oauth WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Michael B. Jones , Brian Campbell , John Bradley , William Denniss | ||
| Last updated | 2019-04-22 (Latest revision 2018-10-19) | ||
| Replaces | draft-jones-oauth-token-binding, draft-campbell-oauth-tbpkce | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 specification enables OAuth 2.0 implementations to apply Token Binding to Access Tokens, Authorization Codes, Refresh Tokens, JWT Authorization Grants, and JWT Client Authentication. This cryptographically binds these tokens to a client's Token Binding key pair, possession of which is proven on the TLS connections over which the tokens are intended to be used. This use of Token Binding protects these tokens from man-in-the-middle and token export and replay attacks.
Authors
Michael B. Jones
Brian Campbell
John Bradley
William Denniss
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)