Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsreq-22.txt

Torsten Lodderstedt <torsten@lodderstedt.net> Sun, 10 May 2020 13:26 UTC

Return-Path: <torsten@lodderstedt.net>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34E423A097D for <oauth@ietfa.amsl.com>; Sun, 10 May 2020 06:26:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lodderstedt.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VNmVt6DStiUZ for <oauth@ietfa.amsl.com>; Sun, 10 May 2020 06:26:08 -0700 (PDT)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2C0B3A097A for <oauth@ietf.org>; Sun, 10 May 2020 06:26:07 -0700 (PDT)
Received: by mail-wm1-x332.google.com with SMTP id g12so15671236wmh.3 for <oauth@ietf.org>; Sun, 10 May 2020 06:26:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lodderstedt.net; s=google; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=l963xqZs5fnf/K8KmgRmTgphGXayUPyZdtIJGoqGYnI=; b=ikaX63w9wRC34XmCS24izyEFC5cLwR7mpZrYq4XZzO3XXHoQ9rJcJ27BaTItmHbziQ zuvycvmzSuYerEaSdAknK2Y0UBSZau/qehRpDbvxiU59O5xVVekNFCNokDnv8wd4GcOs BTGlqa3RCgnGlfUN+AnuNCRN8GDeG8a3v6KPb21UhIoUBy3+3HE9PLy9u4mICcaB4XNt pkJyUvJ6l9QXlGkZ6b3vuJwIV0fYxsGYzedAJZ90xHKm5vNSIDR5xT29WEnIybUDn9iI Y7b1SKotKOxW6udtykiucn6+tiV+8XCJwUTJmtNMQ+GYnyLLCddyUdYna5x+Z7Fgt2D9 xufg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=l963xqZs5fnf/K8KmgRmTgphGXayUPyZdtIJGoqGYnI=; b=tO4jTTJrdJE6p8wZLV1ee/b4J2ojXiEHSj8Hq+JBq643cvslTWUDAcY7dUzHWEgVq1 5oJYAB6BHMR4kAAibM7u4GBZKpC3fOBEZFgMqcH15lQ3+OHOvA1s/r0bQfqKMtd9nan2 uqbMZvQTYo6V4rI3nkwLiKqBPR1QhrZqg0TlXmfKcF9mWf+UvG32b79DoWie+Tai+b7b ASBAY2nNyFwRMjg9XgGtyYy+1F5YXiy4uGUa277bFE8J+hwxC+SJBIExNY+/pHxx5Eeu NWuphEZzmASEiPn9TAqW3wV3iNrAuOnKe5rYC0nHzpp3P3wXO2BIlTz8BHFOYqYp8tq0 HLAA==
X-Gm-Message-State: AGi0PubBOxl2oTtfwE05zTjy21jSNXEuTaaQabMg3y5GfpMApFS+CuYq bDSRKfYO3pYUOyl7/B6VktEp0WB6ZVw=
X-Google-Smtp-Source: APiQypIpHzw6VbOM4WOTttTUtu0J3cMcnOLh1PYwB9GTGihAeQ/q28EGsinstz6jb9lZZf9k/V7yUg==
X-Received: by 2002:a7b:c306:: with SMTP id k6mr25376406wmj.40.1589117165627; Sun, 10 May 2020 06:26:05 -0700 (PDT)
Received: from p200300eb8f301f39e58c5bd211932ee5.dip0.t-ipconnect.de (p200300EB8F301F39E58C5BD211932EE5.dip0.t-ipconnect.de. [2003:eb:8f30:1f39:e58c:5bd2:1193:2ee5]) by smtp.gmail.com with ESMTPSA id n24sm6265859wmi.40.2020.05.10.06.26.04 for <oauth@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 10 May 2020 06:26:04 -0700 (PDT)
From: Torsten Lodderstedt <torsten@lodderstedt.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Sun, 10 May 2020 15:26:03 +0200
References: <158907186941.32364.3855329773244277548@ietfa.amsl.com>
To: oauth <oauth@ietf.org>
In-Reply-To: <158907186941.32364.3855329773244277548@ietfa.amsl.com>
Message-Id: <0F682743-D799-4773-A1E7-09701CEB2BD1@lodderstedt.net>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/4xmHxUpNdc1M35VbycasNRwrUvk>
Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsreq-22.txt
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 May 2020 13:26:12 -0000

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, internet-drafts@ietf.org 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
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth