Internet Engineering Task Force N. Sakimura, Ed.
Internet-Draft Nomura Research Institute
Intended status: Standards Track J. Bradley
Expires: May 07, 2014 Ping Identity
November 03, 2013
Request by JWS ver.1.0 for OAuth 2.0
draft-sakimura-oauth-requrl-04
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 thorugh "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 May 07, 2014.
Copyright Notice
Copyright (c) 2013 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 May 07, 2014 [Page 1]Internet-Draft oauth-json-request November 2013
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 . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Request Object . . . . . . . . . . . . . . . . . . . . . 3
2.2. Request Object URI . . . . . . . . . . . . . . . . . . . 3
3. Request Object . . . . . . . . . . . . . . . . . . . . . . . 4
4. Request Object URI . . . . . . . . . . . . . . . . . . . . . 5
5. Authorization Request . . . . . . . . . . . . . . . . . . . . 6
6. Authorization Server Response . . . . . . . . . . . . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . 7
8. Security Considerations . . . . . . . . . . . . . . . . . . . 7
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
10.1. Normative References . . . . . . . . . . . . . . . . . . 8
10.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
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)
[JWT] whose body holds the JSON encoded OAuth 2.0 authorization
request parameters. The [JWT] can be passed to the authorization
endpoint by reference, in which case the parameter "request_uri" is
used instead of the "request".
Using [JWT] as the request encoding instead of query parameters has
several advantages:
1. The request may be signed so that integrity check may be
implemented. If a suitable algorithm is used for the signing,
then non-repudiation property may be obtained in addition.
2. The request may be encrypted so that end-to-end confidentiality
may be obtained even if in the case TLS connection is terminated
at a gateway or a similar device.
There are a few cases that request by reference is useful such as:
Sakimura & Bradley Expires May 07, 2014 [Page 2]Internet-Draft oauth-json-request November 2013
datatracker.ietf.org