| rfc9126v2.txt | rfc9126.txt | |||
|---|---|---|---|---|
| skipping to change at line 12 ¶ | skipping to change at line 12 ¶ | |||
| Internet Engineering Task Force (IETF) T. Lodderstedt | Internet Engineering Task Force (IETF) T. Lodderstedt | |||
| Request for Comments: 9126 yes.com | Request for Comments: 9126 yes.com | |||
| Category: Standards Track B. Campbell | Category: Standards Track B. Campbell | |||
| ISSN: 2070-1721 Ping Identity | ISSN: 2070-1721 Ping Identity | |||
| N. Sakimura | N. Sakimura | |||
| NAT.Consulting | NAT.Consulting | |||
| D. Tonge | D. Tonge | |||
| Moneyhub Financial Technology | Moneyhub Financial Technology | |||
| F. Skokan | F. Skokan | |||
| Auth0 | Auth0 | |||
| August 2021 | September 2021 | |||
| OAuth 2.0 Pushed Authorization Requests | OAuth 2.0 Pushed Authorization Requests | |||
| Abstract | Abstract | |||
| This document defines the pushed authorization request (PAR) | This document defines the pushed authorization request (PAR) | |||
| endpoint, which allows clients to push the payload of an OAuth 2.0 | endpoint, which allows clients to push the payload of an OAuth 2.0 | |||
| authorization request to the authorization server via a direct | authorization request to the authorization server via a direct | |||
| request and provides them with a request URI that is used as | request and provides them with a request URI that is used as | |||
| reference to the data in a subsequent call to the authorization | reference to the data in a subsequent call to the authorization | |||
| End of changes. 1 change blocks. | ||||
| 1 lines changed or deleted | 1 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||