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

Torsten Lodderstedt <torsten@lodderstedt.net> Sun, 26 April 2020 15:16 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 97A563A0893 for <oauth@ietfa.amsl.com>; Sun, 26 Apr 2020 08:16:41 -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 xrWNyTnoYJ68 for <oauth@ietfa.amsl.com>; Sun, 26 Apr 2020 08:16:39 -0700 (PDT)
Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (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 B563E3A08CF for <oauth@ietf.org>; Sun, 26 Apr 2020 08:16:38 -0700 (PDT)
Received: by mail-wr1-x42c.google.com with SMTP id g13so17456689wrb.8 for <oauth@ietf.org>; Sun, 26 Apr 2020 08:16:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lodderstedt.net; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=4C8GwsnItT5srTUSIA1/+33E78DnMce7rWL4jy3Qeu8=; b=ggakthsxaNYW/ZBsMrzkaCkNpwspELmEu4ZX2M/rbdtPmvnsJblLvBmIJHGWcwTPGH QYFyVtjCJ6d1HYIaZdh+PLpIrX0wtdD0IOZPo+swzKu4IjLGAwd4ynPMcyJ4crx1poO7 pKurNWmN6hG2/iB2e4H/J3w6AA6R1OWYpRcylpVdHEgyx08daiAu+mukkBavhYPrGWqE qEJ6+CMWTpLVfKNmIuDZpjAWJDE8GSmP7tefW9DZYzQhSFQsquqW0gbf1a6jf3ZQK/Gf rNFmes8tUqBo0EbWV3Pkqw3yq1DRrxqHZB3I2baENoUDlALrB92sbhhSPPG2Pfu+gDaL a12A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=4C8GwsnItT5srTUSIA1/+33E78DnMce7rWL4jy3Qeu8=; b=mq3i0nbzbRlu/mbLdbVEocMeWH7c7ggbR9D/XoVbv7DFICeZ/rNXTsVOiMaLGWga9A hy28+YbVuj1s6R1uzxV5JikF44wNqHRij0/9MmtI86DkPH27olP6nixWFlkcE4JCO759 MnRQ17OQ1g0tTXRXJ6nkWGgisBF9kXTtcniadMD0a0kp6Kgs5UA2s80wuWOst6hk7zNn fU3Bs1cX1//UW7iLjPKEhY5ztx6JmC+tcoDE5FXmgiayUGzQVI039ctJAsz4fVPYiiV8 Wq3C6XoTOc59rlw7fJrAEKpuTWY2IK2hNhnRKz+Djcumti0uhEc9gSdriJWk66cDnKSu RYhA==
X-Gm-Message-State: AGi0PubgoOVadBmW16sK5R0QKbF5LvnuesCvb3aL0wm9+12eXpO7O6i6 syrBKXS4Fxw+koqWgEU2fCGuPQ==
X-Google-Smtp-Source: APiQypJHHzoeRmorlSsTfYa1DhRjPmUgyLtGlcH+Bw8Isy3+hFUfvsGqKI5kani7VS7M9Nr3S4J3OQ==
X-Received: by 2002:a05:6000:10c4:: with SMTP id b4mr23005067wrx.203.1587914197104; Sun, 26 Apr 2020 08:16:37 -0700 (PDT)
Received: from p200300eb8f301fbe504ffe40cdc43adf.dip0.t-ipconnect.de (p200300EB8F301FBE504FFE40CDC43ADF.dip0.t-ipconnect.de. [2003:eb:8f30:1fbe:504f:fe40:cdc4:3adf]) by smtp.gmail.com with ESMTPSA id e13sm7739252wrp.15.2020.04.26.08.16.36 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 26 Apr 2020 08:16:36 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Torsten Lodderstedt <torsten@lodderstedt.net>
In-Reply-To: <158732102285.31467.551848692555230905@ietfa.amsl.com>
Date: Sun, 26 Apr 2020 17:16:35 +0200
Cc: oauth <oauth@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1EADC158-FFB3-465E-84ED-B34254F30F79@lodderstedt.net>
References: <158732102285.31467.551848692555230905@ietfa.amsl.com>
To: Nat Sakimura <nat@sakimura.org>, John Bradley <jbradley@yubico.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/BaDi3j6IB12AC_mV46POtZiIR4k>
Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsreq-21.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, 26 Apr 2020 15:16:42 -0000

Hi Nat & John,

I tried to find out how signing & encryption algorithms are determined in the JAR context. 

I just found this note in the history for -07: "Stopped talking about request_object_signing_alg”

I assume you assume this is done via client registration parameters registered in https://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml#client-metadata? Why doesn’t JAR state so?

What is about algorithms supported by the AS? The respective parameters, such as request_object_signing_alg_values_supported are not registered yet in https://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml#authorization-server-metadata.

best regards,
Torsten. 
 

> On 19. Apr 2020, at 20:30, 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-21.txt
> 	Pages           : 31
> 	Date            : 2020-04-19
> 
> 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-21
> https://datatracker.ietf.org/doc/html/draft-ietf-oauth-jwsreq-21
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-oauth-jwsreq-21
> 
> 
> 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