OAuth 2.0 JWT Authorization Request
draft-ietf-oauth-jwsreq-05
OAuth Working Group N. Sakimura, Ed.
Internet-Draft Nomura Research Institute
Intended status: Standards Track J. Bradley
Expires: January 23, 2016 Ping Identity
July 22, 2015
OAuth 2.0 JWT Authorization Request
draft-ietf-oauth-jwsreq-05
Abstract
The authorization request in OAuth 2.0 utilizes query parameter
serialization. This specification defines the authorization request
using JWT serialization. The request is sent through "request"
parameter or by reference through "request_uri" parameter that points
to the JWT, allowing the request to be optionally signed and
encrypted.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 23, 2016.
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Sakimura & Bradley Expires January 23, 2016 [Page 1]
Internet-Draft oauth-jar July 2015
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Request Object . . . . . . . . . . . . . . . . . . . . . 4
2.2. Request Object URI . . . . . . . . . . . . . . . . . . . 4
3. Request Object . . . . . . . . . . . . . . . . . . . . . . . 4
4. Authorization Request . . . . . . . . . . . . . . . . . . . . 6
4.1. Passing a Request Object by Value . . . . . . . . . . . . 7
4.2. Passing a Request Object by Reference . . . . . . . . . . 8
4.2.1. URL Referencing the Request Object . . . . . . . . . 10
4.2.2. Request using the "request_uri" Request Parameter . . 10
4.2.3. Authorization Server Fetches Request Object . . . . . 10
5. Validating JWT-Based Requests . . . . . . . . . . . . . . . . 11
5.1. Encrypted Request Object . . . . . . . . . . . . . . . . 11
5.2. Signed Request Object . . . . . . . . . . . . . . . . . . 11
5.3. Request Parameter Assembly and Validation . . . . . . . . 11
6. Authorization Server Response . . . . . . . . . . . . . . . . 11
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . 12
8. Security Considerations . . . . . . . . . . . . . . . . . . . 12
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
10. Revision History . . . . . . . . . . . . . . . . . . . . . . 13
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
11.1. Normative References . . . . . . . . . . . . . . . . . . 14
11.2. Informative References . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction
The parameters "request" and "request_uri" are introduced as
additional authorization request parameters for the OAuth 2.0
[RFC6749] flows. The "request" parameter is a JSON Web Token (JWT)
[RFC7519] whose JWT Claims Set holds the JSON encoded OAuth 2.0
authorization request parameters. The JWT [RFC7519] can be passed to
the authorization endpoint by reference, in which case the parameter
"request_uri" is used instead of the "request".
Using JWT [RFC7519] as the request encoding instead of query
parameters has several advantages:
1. The request can be signed so that an integrity check can be
implemented. If a suitable algorithm is used for the signing,
then it will provide a good evidence of the approver.
Show full document text