RFC 9396 - OAuth 2.0 Rich Authorization Requests
Published: May 2023
Status: Standards Track
Authors: T. Lodderstedt (yes.com), J. Richer (Bespoke Engineering), B. Campbell (Ping Identity)
Abstract
This document specifies a new parameter authorization_details that is used to carry fine-grained authorization data in OAuth messages.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc9396.
Copyright Notice
Copyright (c) 2023 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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.
Contents
- 1. Introduction
- 1.1. Conventions and Terminology
- 2. Request Parameter "authorization_details"
- 2.1. Authorization Details Types
- 2.2. Common Data Fields
- 3. Authorization Request
- 3.1. Relationship to the "scope" Parameter
- 3.2. Relationship to the "resource" Parameter
- 4. Authorization Response
- 5. Authorization Error Response
- 6. Token Request
- 6.1. Comparing Authorization Details
- 7. Token Response
- 7.1. Enriched Authorization Details in Token Response
- 8. Token Error Response
- 9. Resource Servers
- 9.1. JWT-Based Access Tokens
- 9.2. Token Introspection
- 10. Metadata
- 11. Implementation Considerations
- 11.1. Using Authorization Details in a Certain Deployment
- 11.2. Minimal Implementation Support
- 11.3. Use of Machine-Readable Type Schemas
- 11.4. Large Requests
- 12. Security Considerations
- 13. Privacy Considerations
- 14. IANA Considerations
- 14.1. OAuth Parameters Registration
- 14.2. JSON Web Token Claims Registration
- 14.3. OAuth Token Introspection Response Registration
- 14.4. OAuth Authorization Server Metadata Registration
- 14.5. OAuth Dynamic Client Registration Metadata Registration
- 14.6. OAuth Extensions Error Registration
- 15. References
- 15.1. Normative References
- 15.2. Informative References
Appendix
- Appendix A. Additional Examples
- A.1. OpenID Connect
- A.2. Remote Electronic Signing
- A.3. Access to Tax Data
- A.4. eHealth
Related Resources
- Official Text: RFC 9396 (TXT)
- Official Page: RFC 9396 DataTracker
- Errata: RFC Editor Errata