User-Managed Access (UMA) Profile of OAuth 2.0
draft-hardjono-oauth-umacore-13
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Thomas Hardjono , Eve Maler , Maciej Machulak , Domenico Catalano | ||
| Last updated | 2015-10-06 (Latest revision 2015-04-04) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
User-Managed Access (UMA) is a profile of OAuth 2.0. UMA defines how resource owners can control protected-resource access by clients operated by arbitrary requesting parties, where the resources reside on any number of resource servers, and where a centralized authorization server governs access based on resource owner policies.
Authors
Thomas Hardjono
Eve Maler
Maciej Machulak
Domenico Catalano
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)