OAuth 2.0 JWT Authorization Request
draft-ietf-oauth-jwsreq-07

The information below is for an old version of the document
Document Type Expired Internet-Draft (oauth WG)
Authors Nat Sakimura  , John Bradley 
Last updated 2016-07-22 (latest revision 2016-01-19)
Replaces draft-sakimura-oauth-requrl
Stream Internet Engineering Task Force (IETF)
Formats
Expired & archived
plain text xml pdf htmlized bibtex
Reviews
SECDIR Last Call Review (of -30): Serious Issues
GENART Last Call Review (of -30): Ready
GENART Last Call Review (of -11): Not Ready
SECDIR Last Call Review (of -11): Ready
OPSDIR Last Call Review (of -11): Has Nits
GENART Telechat Review (of -09): Not Ready
SECDIR Telechat Review (of -09): Has Issues
OPSDIR Telechat Review (of -09): Has Nits
Stream WG state In WG Last Call
Document shepherd Hannes Tschofenig
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Email authors Email WG IPR References Referenced by Nits

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-oauth-jwsreq-07.txt

Abstract

The authorization request in OAuth 2.0 [RFC6749] utilizes query parameter serialization, which means that parameters are encoded in the URI of the request. This document introduces the ability to send request parameters in form of a JSON Web Token (JWT) instead, which allows the request to be signed and encrypted. using JWT serialization. The request is sent by value or by reference.

Authors

Nat Sakimura (n-sakimura@nri.co.jp)
John Bradley (ve7jtb@ve7jtb.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)

RFC Editor IASA & IETF LLC IETF Trust IRTF IETF IESG IAB IANA Privacy Statement IETF Tools