IETF RFC 9396
[ACTIVE]
OAuth 2.0 Rich Authorization Requests
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 38
- Abstract
- This document specifies a new parameter authorization_details that is used to carry fine-grained authorization data in OAuth messages.
- Publication Date
- 2023-05-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC9396- Link
- https://doi.org/10.17487/RFC9396
- Author(s)
- Torsten LodderstedtJustin RicherBrian Campbell
- Keyword(s)
- Security, OAuth
Latest version of IETF RFC 9396
Document Versions — IETF RFC 9396
-
▶ IETF RFC 9396 (2023-05-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 7519 [Active*]
- IETF RFC 7662 [Active*]
- IETF RFC 8174 [Active*]
- IETF RFC 8414 [Active*]
- RFC8628 — RFC8628 EXTERNAL
- IETF RFC 8707 [Active*]
Bibliographic Reference(s)
- ETSI.TS-119-432.2019 — ETSI EXTERNAL
- IANA, "OAuth Parameters", <https://www.iana.org/assignments/oauth-parameters>. EXTERNAL
- Sakimura, N., Bradley, J., Jones, M., de Medeiros, B., and C. Mortimore, "OpenID Connect Core 1.0 incorporating errata set 1", 8 November 2014, <https://openid.net/specs/openid-connect-core-1_0.html>. EXTERNAL
- Fernandez, G., Walter, F., Nennker, A., Tonge, D., and B. Campbell, "OpenID Connect Client-Initiated Backchannel Authentication Flow - Core 1.0", 1 September 2021, <https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0.html>. EXTERNAL
- OpenJS Foundation, "JSON Schema", <https://json-schema.org/>. EXTERNAL
- Lodderstedt, T., "Transaction Authorization or why we need to re-think OAuth scopes", 20 April 2019, <https://medium.com/oauth-2/transaction-authorization-or-why-we-need-to-re-think-oauth-scopes-2326e2038948>. EXTERNAL
- Cloud Signature Consortium, "Architectures and protocols for remote signature applications", Version 1.0.4.0, June 2019, <https://cloudsignatureconsortium.org/wp-content/uploads/2020/01/CSC_API_V1_1.0.4.0.pdf>. EXTERNAL
- IETF RFC 20 [Active*]
- IETF RFC 6749 [Active*]
- IETF RFC 7591 [Active*]
- IETF RFC 8259 [Active*]
- IETF RFC 9101 [Active*]
- IETF RFC 9126 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC9396.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 9396, OAuth 2.0 Rich Authorization Requests. Available at https://doi.org/10.17487/RFC9396
Snippet:
IETF RFC 9396, OAuth 2.0 Rich Authorization Requests. Available at https://doi.org/10.17487/RFC9396
HTML (ISO 690 compliant)
Preview:
IETF RFC 9396, OAuth 2.0 Rich Authorization Requests. Available at https://doi.org/10.17487/RFC9396
Snippet:
<span class="citation"><cite>IETF RFC 9396</cite>, OAuth 2.0 Rich Authorization Requests. Available at <a href="https://doi.org/10.17487/RFC9396" target="_blank" rel="noopener">https://doi.org/10.17487/RFC9396</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 9396, OAuth 2.0 Rich Authorization Requests
doi: 10.17487/RFC9396
url: https://doi.org/10.17487/RFC9396
doi: 10.17487/RFC9396
url: https://doi.org/10.17487/RFC9396
Snippet:
<li> <cite id="bib-rfc9396">IETF RFC 9396</cite>, OAuth 2.0 Rich Authorization Requests <span class="doi">10.17487/RFC9396</span> </li>
Referenced By
- IETF RFC 9700 [Active*]