OAuth 2.0 Security Best Current Practice
draft-ietf-oauth-security-topics-13
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Torsten Lodderstedt , John Bradley , Andrey Labunets , Daniel Fett | ||
| Last updated | 2020-01-09 (Latest revision 2019-07-08) | ||
| Replaces | draft-lodderstedt-oauth-security-topics | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
ARTART Last Call review
(of
-25)
by Russ Housley
Almost ready
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Associated WG milestone |
|
||
| Document shepherd | Hannes Tschofenig | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | Hannes Tschofenig <hannes.tschofenig@arm.com> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes best current security practice for OAuth 2.0. It updates and extends the OAuth 2.0 Security Threat Model to incorporate practical experiences gathered since OAuth 2.0 was published and covers new threats relevant due to the broader application of OAuth 2.0.
Authors
Torsten Lodderstedt
John Bradley
Andrey Labunets
Daniel Fett
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)