Thanks for the quick check. I updated the draft. Also, Mike Jones pointed me that It MUST also reject the request if the request object uses "alg":"none". needs to be added, so I did.
On Thu, Jul 2, 2020 at 2:30 AM Tangui Le Pense <tangui.lepense= 40mail...@dmarc.ietf.org> wrote: > Hello, > > There seems to be a typo: > > 9.2 and 9.3: "require_signed_request_objects" > > 10.5: "require_signed_request_object" > > Regards, > > -- > > Tangui > > 01.07.2020 16:14, internet-dra...@ietf.org пишет: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > This draft is a work item of the Web Authorization Protocol WG of the > IETF. > > > > Title : The OAuth 2.0 Authorization Framework: JWT > Secured Authorization Request (JAR) > > Authors : Nat Sakimura > > John Bradley > > Filename : draft-ietf-oauth-jwsreq-24.txt > > Pages : 33 > > Date : 2020-07-01 > > > > Abstract: > > The authorization request in OAuth 2.0 described in RFC 6749 utilizes > > query parameter serialization, which means that Authorization Request > > parameters are encoded in the URI of the request and sent through > > user agents such as web browsers. While it is easy to implement, it > > means that (a) the communication through the user agents are not > > integrity protected and thus the parameters can be tainted, and (b) > > the source of the communication is not authenticated. Because of > > these weaknesses, several attacks to the protocol have now been put > > forward. > > > > This document introduces the ability to send request parameters in a > > JSON Web Token (JWT) instead, which allows the request to be signed > > with JSON Web Signature (JWS) and encrypted with JSON Web Encryption > > (JWE) so that the integrity, source authentication and > > confidentiality property of the Authorization Request is attained. > > The request can be sent by value or by reference. > > > > > > The IETF datatracker status page for this draft is: > > https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/ > > > > There are also htmlized versions available at: > > https://tools.ietf.org/html/draft-ietf-oauth-jwsreq-24 > > https://datatracker.ietf.org/doc/html/draft-ietf-oauth-jwsreq-24 > > > > A diff from the previous version is available at: > > https://www.ietf.org/rfcdiff?url2=draft-ietf-oauth-jwsreq-24 > > > > > > Please note that it may take a couple of minutes from the time of > submission > > until the htmlized version and diff are available at tools.ietf.org. > > > > Internet-Drafts are also available by anonymous FTP at: > > ftp://ftp.ietf.org/internet-drafts/ > > > > > > _______________________________________________ > > OAuth mailing list > > OAuth@ietf.org > > https://www.ietf.org/mailman/listinfo/oauth > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth > -- Nat Sakimura (=nat) Chairman, OpenID Foundation http://nat.sakimura.org/ @_nat_en
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
