Sender Constrained JWT for OAuth 2.0
draft-sakimura-oauth-rjwtprof-06
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Nat Sakimura , Kepeng Li | ||
| Last updated | 2016-04-21 (Latest revision 2015-10-19) | ||
| Replaced by | draft-sakimura-oauth-jpop | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-sakimura-oauth-jpop | |
| 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 discussion document describes a method to indicate a sender constraint within JWT. It could potentially be incorporated into Proof-Of-Possession Semantics for JSON Web Tokens(JWTs) [POPS]. This document was created in response to the WGLC of it.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)