The following errata report has been submitted for RFC9126,
"OAuth 2.0 Pushed Authorization Requests".
--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7254

--------------------------------------
Type: Editorial
Reported by: Joseph Heenan <jos...@heenan.me.uk>

Section: 1.1

Original Text
-------------
POST /as/par HTTP/1.1
Host: as.example.com
Content-Type: application/x-www-form-urlencoded

&response_type=code
&client_id=CLIENT1234&state=duk681S8n00GsJpe7n9boxdzen
<...>

Corrected Text
--------------
POST /as/par HTTP/1.1
Host: as.example.com
Content-Type: application/x-www-form-urlencoded

response_type=code
&client_id=CLIENT1234&state=duk681S8n00GsJpe7n9boxdzen
<...>

Notes
-----
In the 'Introductory Example', the POST body to the par endpoint contains an 
unnecessary '&' at the start. (It's perhaps technically valid, but could 
potentially confuse readers.)

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC9126 (draft-ietf-oauth-par-10)
--------------------------------------
Title               : OAuth 2.0 Pushed Authorization Requests
Publication Date    : September 2021
Author(s)           : T. Lodderstedt, B. Campbell, N. Sakimura, D. Tonge, F. 
Skokan
Category            : PROPOSED STANDARD
Source              : Web Authorization Protocol
Area                : Security
Stream              : IETF
Verifying Party     : IESG

_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

Reply via email to