OAuth 2.0 Rich Authorization Requests
draft-ietf-oauth-rar-01

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01

Web Authorization Protocol                                T. Lodderstedt
Internet-Draft                                                   yes.com
Intended status: Standards Track                               J. Richer
Expires: 22 August 2020                              Bespoke Engineering
                                                             B. Campbell
                                                           Ping Identity
                                                        19 February 2020

                 OAuth 2.0 Rich Authorization Requests
                        draft-ietf-oauth-rar-01

Abstract

   This document specifies a new parameter "authorization_details" that
   is used to carry fine grained authorization data in the OAuth
   authorization request.

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 August 2020.

Copyright Notice

   Copyright (c) 2020 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 (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.

Lodderstedt, et al.      Expires 22 August 2020                 [Page 1]
Internet-Draft                  oauth-rar                  February 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions and Terminology . . . . . . . . . . . . . . .   4
   2.  Request parameter "authorization_details" . . . . . . . . . .   4
     2.1.  Authorization data elements types . . . . . . . . . . . .   6
     2.2.  Relationship to "scope" parameter . . . . . . . . . . . .   8
       2.2.1.  Scope value "openid" and "claims" parameter . . . . .   9
     2.3.  Relationship to "resource" parameter  . . . . . . . . . .   9
   3.  Using "authorization_details" . . . . . . . . . . . . . . . .  11
     3.1.  Authorization Request . . . . . . . . . . . . . . . . . .  11
     3.2.  Authorization Request Processing  . . . . . . . . . . . .  14
     3.3.  Token Request . . . . . . . . . . . . . . . . . . . . . .  15
     3.4.  Token Response  . . . . . . . . . . . . . . . . . . . . .  15
       3.4.1.  Token Content . . . . . . . . . . . . . . . . . . . .  16
     3.5.  Token Introspection Request . . . . . . . . . . . . . . .  18
     3.6.  Token Introspection Response  . . . . . . . . . . . . . .  18
   4.  Metadata  . . . . . . . . . . . . . . . . . . . . . . . . . .  19
   5.  Implementation Considerations . . . . . . . . . . . . . . . .  20
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  20
   7.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  20
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  21
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
   10. Normative References  . . . . . . . . . . . . . . . . . . . .  21
   11. Informative References  . . . . . . . . . . . . . . . . . . .  22
   Appendix A.  Additional Examples  . . . . . . . . . . . . . . . .  23
     A.1.  OpenID Connect  . . . . . . . . . . . . . . . . . . . . .  24
     A.2.  Remote Electronic Signing . . . . . . . . . . . . . . . .  25
     A.3.  Access to Tax Data  . . . . . . . . . . . . . . . . . . .  26
     A.4.  eHealth . . . . . . . . . . . . . . . . . . . . . . . . .  27
   Appendix B.  Document History . . . . . . . . . . . . . . . . . .  29
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  30

1.  Introduction

   The OAuth 2.0 authorization framework [RFC6749] defines the parameter
   "scope" that allows OAuth clients to specify the requested scope,
   i.e., the permission, of an access token.  This mechanism is
   sufficient to implement static scenarios and coarse-grained
   authorization requests, such as "give me read access to the resource
   owner's profile" but it is not sufficient to specify fine-grained
   authorization requirements, such as "please let me make a payment