OAuth 2.0 Software Statement
draft-hunt-oauth-software-statement-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Phil Hunt , Anthony Nadalin | ||
| Last updated | 2014-03-31 (Latest revision 2013-09-27) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
This specification defines a JWT authorization assertion known as a 'software statment' for use in an OAuth protected environment. A software statement is a JWT assertion used by an OAuth client to provide both informational and OAuth protocol related assertions that aid service providers to recognize OAuth client software and its expected behaviour within an OAuth Framework protected resource environment.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)