OAuth 2.0 Pushed Authorization Requests
draft-ietf-oauth-par-04

Document Type Active Internet-Draft (oauth WG)
Authors Torsten Lodderstedt  , Brian Campbell  , Nat Sakimura  , Dave Tonge  , Filip Skokan 
Last updated 2020-09-18
Stream IETF
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Web Authorization Protocol                                T. Lodderstedt
Internet-Draft                                                   yes.com
Intended status: Standards Track                             B. Campbell
Expires: 22 March 2021                                     Ping Identity
                                                             N. Sakimura
                                                          NAT.Consulting
                                                                D. Tonge
                                           Moneyhub Financial Technology
                                                               F. Skokan
                                                                   Auth0
                                                       18 September 2020

                OAuth 2.0 Pushed Authorization Requests
                        draft-ietf-oauth-par-04

Abstract

   This document defines the pushed authorization request endpoint,
   which allows clients to push the payload of an OAuth 2.0
   authorization request to the authorization server via a direct
   request and provides them with a request URI that is used as
   reference to the data in a subsequent call to the authorization
   endpoint.

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 https://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 22 March 2021.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Lodderstedt, et al.       Expires 22 March 2021                 [Page 1]
Internet-Draft                  OAuth PAR                 September 2020

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://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 the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Introductory Example  . . . . . . . . . . . . . . . . . .   4
     1.2.  Conventions and Terminology . . . . . . . . . . . . . . .   5
   2.  Pushed Authorization Request Endpoint . . . . . . . . . . . .   5
     2.1.  Request . . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.2.  Successful Response . . . . . . . . . . . . . . . . . . .   8
     2.3.  Error Response  . . . . . . . . . . . . . . . . . . . . .   9
     2.4.  Management of Client Redirect URIs  . . . . . . . . . . .  10
   3.  The "request" Request Parameter . . . . . . . . . . . . . . .  11
   4.  Authorization Request . . . . . . . . . . . . . . . . . . . .  13
   5.  Authorization Server Metadata . . . . . . . . . . . . . . . .  13
   6.  Client Metadata . . . . . . . . . . . . . . . . . . . . . . .  14
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
     7.1.  Request URI Guessing  . . . . . . . . . . . . . . . . . .  14
     7.2.  Open Redirection  . . . . . . . . . . . . . . . . . . . .  14
     7.3.  Request Object Replay . . . . . . . . . . . . . . . . . .  15
     7.4.  Client Policy Change  . . . . . . . . . . . . . . . . . .  15
     7.5.  Request URI Swapping  . . . . . . . . . . . . . . . . . .  15
   8.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  15
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  15
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
     10.1.  OAuth Authorization Server Metadata  . . . . . . . . . .  16
     10.2.  OAuth Dynamic Client Registration Metadata . . . . . . .  16
     10.3.  OAuth URI Registration . . . . . . . . . . . . . . . . .  16
   11. Normative References  . . . . . . . . . . . . . . . . . . . .  17
   12. Informative References  . . . . . . . . . . . . . . . . . . .  17
   Appendix A.  Document History . . . . . . . . . . . . . . . . . .  19
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  20

1.  Introduction

   Pushed authorization requests (PAR), defined by this document, enable
   OAuth [RFC6749] clients to push the payload of an authorization
Show full document text