RFC 9396: OAuth 2.0 Rich Authorization Requests

request for comments publication
Place request_for_comments Q121037502
Press Enter · cited answer in seconds

RFC 9396: OAuth 2.0 Rich Authorization Requests

Summary

RFC 9396: OAuth 2.0 Rich Authorization Requests is a Request for Comments[1].

Key Facts

  • RFC 9396: OAuth 2.0 Rich Authorization Requests's instance of is recorded as OAuth 2.0 Rich Authorization Requests — instance of (P31): Request for Comments[2].
  • RFC 9396: OAuth 2.0 Rich Authorization Requests's publisher is recorded as OAuth 2.0 Rich Authorization Requests — publisher (P123): Internet Engineering Task Force[3].
  • RFC 9396: OAuth 2.0 Rich Authorization Requests's DOI is recorded as 10.17487/RFC9396[4].
  • RFC 9396: OAuth 2.0 Rich Authorization Requests's language of work or name is recorded as OAuth 2.0 Rich Authorization Requests — language of work or name (P407): English[5].
  • RFC 9396: OAuth 2.0 Rich Authorization Requests's publication date is recorded as +2023-05-01T00:00:00Z[6].
  • RFC 9396: OAuth 2.0 Rich Authorization Requests's RfC ID is recorded as 9396[7].
  • RFC 9396: OAuth 2.0 Rich Authorization Requests's main subject is recorded as OAuth 2.0 Rich Authorization Requests — main subject (P921): OAuth 2[8].
  • RFC 9396: OAuth 2.0 Rich Authorization Requests's work available at URL is recorded as https://tools.ietf.org/html/rfc9396[9].
  • RFC 9396: OAuth 2.0 Rich Authorization Requests's title is recorded as OAuth 2.0 Rich Authorization Requests[10].
  • RFC 9396: OAuth 2.0 Rich Authorization Requests's author name string is recorded as T. Lodderstedt[11].
  • RFC 9396: OAuth 2.0 Rich Authorization Requests's author name string is recorded as J. Richer[12].
  • RFC 9396: OAuth 2.0 Rich Authorization Requests's author name string is recorded as B. Campbell[13].

Body

Designation and Status

RFC 9396: OAuth 2.0 Rich Authorization Requests's instance of is recorded as OAuth 2.0 Rich Authorization Requests — instance of (P31): Request for Comments[2].

References

Programmatic citations — every numbered marker resolves to a verifiable graph row below.

Direct Wikidata claims

  1. [2] . RFC Index. Retrieved . wikidata.org.
  2. [3] . RFC Index. Retrieved . wikidata.org.
  3. [4] . RFC Index. Retrieved . wikidata.org.
  4. [5] . RFC Index. Retrieved . wikidata.org.
  5. [6] . RFC Index. Retrieved . wikidata.org.
  6. [7] . RFC Index. Retrieved . wikidata.org.
  7. [8] . wikidata.org.
  8. [9] . RFC Index. Retrieved . wikidata.org.
  9. [10] . RFC Index. Retrieved . wikidata.org.
  10. [11] . RFC Index. Retrieved . wikidata.org.
  11. [12] . RFC Index. Retrieved . wikidata.org.
  12. [13] . RFC Index. Retrieved . wikidata.org.

Class ancestry

  1. [1] . Wikidata. wikidata.org.

📑 Cite this page

Use these citations when quoting this entity in research, articles, AI prompts, or wherever provenance matters. We aggregate Wikidata + Wikipedia + authoritative open-data sources; the stitched, scored, cross-referenced view is what 4ort.xyz contributes.

APA 4ort.xyz Knowledge Graph. (2026). RFC 9396: OAuth 2.0 Rich Authorization Requests. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-9396-oauth-2-0-rich-authorization-requests
MLA “RFC 9396: OAuth 2.0 Rich Authorization Requests.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-9396-oauth-2-0-rich-authorization-requests.
BibTeX @misc{4ortxyz_rfc-9396-oauth-2-0-rich-authorization-requests_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 9396: OAuth 2.0 Rich Authorization Requests}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-9396-oauth-2-0-rich-authorization-requests}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 9396: OAuth 2.0 Rich Authorization Requests — https://4ort.xyz/entity/rfc-9396-oauth-2-0-rich-authorization-requests (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-9396-oauth-2-0-rich-authorization-requests · Last refreshed: