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

Torsten Lodderstedt <torsten@lodderstedt.net> Fri, 01 May 2020 17:56 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 AB10D3A18D8 for <oauth@ietfa.amsl.com>; Fri, 1 May 2020 10:56:54 -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=unavailable 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 pwitVG-9cJCc for <oauth@ietfa.amsl.com>; Fri, 1 May 2020 10:56:50 -0700 (PDT)
Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) (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 8432A3A18D9 for <oauth@ietf.org>; Fri, 1 May 2020 10:56:50 -0700 (PDT)
Received: by mail-wr1-x431.google.com with SMTP id l18so1627746wrn.6 for <oauth@ietf.org>; Fri, 01 May 2020 10:56:50 -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=jINgiFeCGvYMG+bk9sC4rHD/ZvlQOyOujyARFLn2Gho=; b=EKZoTIJ4+g9G8WjiL9o9vuDv0ppiToXAXUjWkpuxhTIeAwc4jVB2zSU6eS73bhp5eC XA/nlXN+ASLqCA0W/Rof+52IcHfQfSv+MsITMVhHFXJidgKp5MqkdQ/acjZsXRUMQon+ q4jhrO1qwRWsP1/bCX3TyCU5WrTkFxQ8L+M3AU+koD1rM0HMx/EsLBWJ1CH3Sox4Jvhe Bi1Mnu5kawp6UPvLNdlbm+g8YpfIENZ3SnvHjLko8qtXGcmPTpCiqWkmUVayP6xWKzTg do6zdxicLm08SaA29/uRdPKt+7wLu1Coh5SAQ9CraVILWrzM4SIklVmsJYlI82fQfnGX zN4g==
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=jINgiFeCGvYMG+bk9sC4rHD/ZvlQOyOujyARFLn2Gho=; b=TR0qoS026+WG+aWk+K/b37F29L/WWZo5KtYlHA2yJ0L5MSpXav3yhG7QZdXky7ydZb mCDAdIbvAxGUOTCWIQBvieADy28PtYgjmapkW+456YJlGTM6b1tZ1+BKryNv+QD/ur0l 9r4GCZ/LeYbeObrAElfCyua59Qi0UnMaMX3m6Nwgtex2NWqGnOJ/CeJ4pAT62tCM8S/9 wy19s5NQ02yEq4u/G5oU7GFQ9KFC4zgoqZw+JkUEDD3M7fqGoefnr3UDHxcJauK+VF59 CveGkX89+4hNBmYez8oyS04Zd+m4C0JozIlC+SB0sbu+CPhKxbV1vTj5uaViiy+Z8Hep URGw==
X-Gm-Message-State: AGi0PuYLCFLaifrBvJAtVB4NBc6qIoNtgs8QagjQui8RTWQQkCuNvOAn Bi1W6LJICculgxv4/0wRsM9Ahg==
X-Google-Smtp-Source: APiQypLlYuYNPnaDDowE1Ca2BJDhWYNqHNEjlyymxz21OlzBIKv23BMJzlX37b+aUXID1pb6WkCKdg==
X-Received: by 2002:a5d:45cf:: with SMTP id b15mr5115504wrs.78.1588355808775; Fri, 01 May 2020 10:56:48 -0700 (PDT)
Received: from p200300eb8f301f21f5f78f2c395685eb.dip0.t-ipconnect.de (p200300EB8F301F21F5F78F2C395685EB.dip0.t-ipconnect.de. [2003:eb:8f30:1f21:f5f7:8f2c:3956:85eb]) by smtp.gmail.com with ESMTPSA id 2sm832675wre.25.2020.05.01.10.56.47 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 May 2020 10:56:48 -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: <DM6PR00MB068419E97B418CB70196A99BF5AB0@DM6PR00MB0684.namprd00.prod.outlook.com>
Date: Fri, 1 May 2020 19:56:47 +0200
Cc: "bcampbell@pingidentity.com" <bcampbell@pingidentity.com>, John Bradley <jbradley@yubico.com>, Nat Sakimura <nat@sakimura.org>, oauth <oauth@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <856DF98C-748B-4DF8-A81D-B146CB9CB629@lodderstedt.net>
References: <DM6PR00MB068419E97B418CB70196A99BF5AB0@DM6PR00MB0684.namprd00.prod.outlook.com>
To: Mike Jones <Michael.Jones=40microsoft.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/k1tVMqSscDxy9LiKSfMMvPF1k4M>
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: Fri, 01 May 2020 17:56:55 -0000

I created a pull request https://bitbucket.org/Nat/oauth-jwsreq/pull-requests/4 

> On 1. May 2020, at 18:16, Mike Jones <Michael.Jones=40microsoft.com@dmarc.ietf.org> wrote:
> 
> I believe that Nat hasn’t yet published the JAR updates that Brian made.  Do we want to add this text to the editor’s draft before publishing?
>  
>                                                        -- Mike
>  
> From: Torsten Lodderstedt <torsten=40lodderstedt.net@dmarc.ietf.org> 
> Sent: Friday, May 1, 2020 2:37 AM
> To: Mike Jones <Michael.Jones@microsoft.com>
> Cc: John Bradley <jbradley@yubico.com>om>; Nat Sakimura <nat@sakimura.org>rg>; oauth <oauth@ietf.org>
> Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsreq-21.txt
>  
> Thanks Mike.
>  
> I suggest to add text to JAR describing use of this registry values to determine the request object signing and encryption algorithms. 
>  
> Mike Jones <Michael.Jones=40microsoft.com@dmarc.ietf.org> schrieb am Mi. 29. Apr. 2020 um 01:38:
> “request_object_signing_alg_values_supported” and other AS Metadata values defined by OpenID Connect Discovery are now registered at https://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml#authorization-server-metadata.
>  
>                                                           -- Mike
>  
> From: nat=sakimura.org@mg.sakimura.org <nat=sakimura.org@mg.sakimura.org> On Behalf Of Nat Sakimura
> Sent: Sunday, April 26, 2020 10:29 AM
> To: Torsten Lodderstedt <torsten=40lodderstedt.net@dmarc.ietf.org>rg>; John Bradley <jbradley@yubico.com>om>; Mike Jones <Michael.Jones@microsoft.com>
> Cc: oauth <oauth@ietf.org>
> Subject: [EXTERNAL] Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsreq-21.txt
>  
> Thanks Mike. 
>  
> Right in as much as I never expected JAR to take this long, I was expecting the errata to be published and these params to be registered long before as well :-) But it may be a good sign that we Identiterati are all so busy these days. 
>  
> Nat Sakimura 
> Chairman, OpenID Foundation 
> https://nat.sakimura.org
> 2020年4月27日 2:17 +0900、Mike Jones <Michael.Jones@microsoft.com> のメール:
> 
> The next errata version of OpenID Connect Discovery will register the parameter request_object_signing_alg_values_supported and other parameters not previously registered. Seehttps://openid.net/specs/openid-connect-discovery-1_0-29.html for the latest published errata draft.
> 
> I can make a request for early registration if it would be useful.
> 
> -- Mike
> 
> -----Original Message-----
> From: OAuth <oauth-bounces@ietf.org> On Behalf Of Torsten Lodderstedt
> Sent: Sunday, April 26, 2020 8:17 AM
> To: Nat Sakimura <nat@sakimura.org>rg>; John Bradley <jbradley@yubico.com>
> Cc: oauth <oauth@ietf.org>
> Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsreq-21.txt
> 
> 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 inhttps://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
> 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth