[OAUTH-WG] Last Call: <draft-ietf-oauth-jwsreq-30.txt> (The OAuth 2.0 Authorization Framework: JWT Secured Authorization Request (JAR)) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Fri, 18 September 2020 18:26 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
CC: rdd@cert.org, oauth-chairs@ietf.org, draft-ietf-oauth-jwsreq@ietf.org, Hannes.Tschofenig@gmx.net, oauth@ietf.org
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <160045359121.1336.16663002308510342861@ietfa.amsl.com>
Date: Fri, 18 Sep 2020 11:26:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/Dxl0FhJXIPw-f-VHHtYm0xTrJfE>
Subject: [OAUTH-WG] Last Call: <draft-ietf-oauth-jwsreq-30.txt> (The OAuth 2.0 Authorization Framework: JWT Secured Authorization Request (JAR)) to Proposed Standard

The IESG has received a request from the Web Authorization Protocol WG
(oauth) to consider the following document: - 'The OAuth 2.0 Authorization
Framework: JWT Secured Authorization
   Request (JAR)'
  <draft-ietf-oauth-jwsreq-30.txt> as Proposed Standard

This document is being brought back for a second IETF Last Call to confirm 
consensus on changes made in response to multiple IESG Reviews in 2017 and 2019.

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2020-10-02. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

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 is 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 file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/



No IPR declarations have been submitted directly on this I-D.

[OAUTH-WG] Last Call: <draft-ietf-oauth-jwsreq-30… The IESG