OAuth 2.0 Rich Authorization Requests
draft-ietf-oauth-rar-03
Web Authorization Protocol T. Lodderstedt
Internet-Draft yes.com
Intended status: Standards Track J. Richer
Expires: 21 April 2021 Bespoke Engineering
B. Campbell
Ping Identity
18 October 2020
OAuth 2.0 Rich Authorization Requests
draft-ietf-oauth-rar-03
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 21 April 2021.
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 21 April 2021 [Page 1]
Internet-Draft oauth-rar October 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 . . . . . . . . . . . . 5
2.2. Authorization Data Types . . . . . . . . . . . . . . . . 8
2.3. Relationship to "scope" parameter . . . . . . . . . . . . 9
2.3.1. Scope value "openid" and "claims" parameter . . . . . 9
2.4. Relationship to "resource" parameter . . . . . . . . . . 9
2.4.1. Authorization Request . . . . . . . . . . . . . . . . 10
2.4.2. Token Request . . . . . . . . . . . . . . . . . . . . 10
3. Using "authorization_details" . . . . . . . . . . . . . . . . 12
3.1. Authorization Request . . . . . . . . . . . . . . . . . . 12
3.2. Authorization Request Processing . . . . . . . . . . . . 15
3.3. Token Request . . . . . . . . . . . . . . . . . . . . . . 16
3.4. Token Response . . . . . . . . . . . . . . . . . . . . . 16
3.4.1. Enriched authorization details in Token Response . . 17
3.5. Token Content . . . . . . . . . . . . . . . . . . . . . . 20
3.6. Token Introspection Request . . . . . . . . . . . . . . . 22
3.7. Token Introspection Response . . . . . . . . . . . . . . 22
4. Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5. Implementation Considerations . . . . . . . . . . . . . . . . 24
6. Security Considerations . . . . . . . . . . . . . . . . . . . 24
7. Privacy Considerations . . . . . . . . . . . . . . . . . . . 24
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
10. Normative References . . . . . . . . . . . . . . . . . . . . 25
11. Informative References . . . . . . . . . . . . . . . . . . . 26
Appendix A. Additional Examples . . . . . . . . . . . . . . . . 28
A.1. OpenID Connect . . . . . . . . . . . . . . . . . . . . . 28
A.2. Remote Electronic Signing . . . . . . . . . . . . . . . . 29
A.3. Access to Tax Data . . . . . . . . . . . . . . . . . . . 30
A.4. eHealth . . . . . . . . . . . . . . . . . . . . . . . . . 31
Appendix B. Document History . . . . . . . . . . . . . . . . . . 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35
1. Introduction
The OAuth 2.0 authorization framework [RFC6749] defines the parameter
"scope" that allows OAuth clients to specify the requested scope,
Show full document text