The OAuth 2.1 Authorization Framework
draft-ietf-oauth-v2-1-11
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Dick Hardt , Aaron Parecki , Torsten Lodderstedt | ||
| Last updated | 2024-11-15 (Latest revision 2024-05-14) | ||
| Replaces | draft-parecki-oauth-v2-1 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Associated WG milestone |
|
||
| 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
The OAuth 2.1 authorization framework enables an application to obtain limited access to a protected resource, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and an authorization service, or by allowing the application to obtain access on its own behalf. This specification replaces and obsoletes the OAuth 2.0 Authorization Framework described in RFC 6749 and the Bearer Token Usage in RFC 6750.
Authors
Dick Hardt
Aaron Parecki
Torsten Lodderstedt
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)