Torsten, Thanks. I just updated the draft.
Best, Nat Sakimura On Sun, May 10, 2020 at 10:26 PM Torsten Lodderstedt <torsten= [email protected]> wrote: > I just read over the diff between -21 and -22 and realised the example in > Section 5.2.2. > > https://server.example.com/authorize? > response_type=code%20id_token > &client_id=s6BhdRkqt3 > &request_uri=https%3A%2F%2Ftfp.example.org%2Frequest.jwt > %2FGkurKxf5T0Y-mnPFCHqWOMiZi4VS138cQO_V7PZHAdM > > still has the “response_type" parameter. I think this parameter should be > removed. > > > > > On 10. May 2020, at 02:51, [email protected] wrote: > > > > > > 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-22.txt > > Pages : 32 > > Date : 2020-05-07 > > > > 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-22 > > https://datatracker.ietf.org/doc/html/draft-ietf-oauth-jwsreq-22 > > > > A diff from the previous version is available at: > > https://www.ietf.org/rfcdiff?url2=draft-ietf-oauth-jwsreq-22 > > > > > > 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 > > [email protected] > > https://www.ietf.org/mailman/listinfo/oauth > > _______________________________________________ > OAuth mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/oauth > -- Nat Sakimura (=nat) Chairman, OpenID Foundation http://nat.sakimura.org/ @_nat_en
_______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
