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

Torsten Lodderstedt <torsten@lodderstedt.net> Fri, 01 May 2020 09:37 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 BBD673A0D80 for <oauth@ietfa.amsl.com>; Fri, 1 May 2020 02:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, 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 ZRYd4IK0vRzm for <oauth@ietfa.amsl.com>; Fri, 1 May 2020 02:37:07 -0700 (PDT)
Received: from mail-ua1-x931.google.com (mail-ua1-x931.google.com [IPv6:2607:f8b0:4864:20::931]) (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 C51833A0D6E for <oauth@ietf.org>; Fri, 1 May 2020 02:37:06 -0700 (PDT)
Received: by mail-ua1-x931.google.com with SMTP id t8so3569651uap.3 for <oauth@ietf.org>; Fri, 01 May 2020 02:37:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lodderstedt.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HaWojZ154ty1BuXuO0+YO3eSKuA4lL2H6ORoaKrmkaI=; b=5awIM4iy4PfIWH8iLvP2aZ1BguuIoFxQNnU9m4l48MLuUcP9lQbPr644tU5GXS8Il7 kDxPQWCHUPbildXKpAgsOuC5kQAqu3ZJPt6thfGsRSVBKeQqMUbutWiQzvagCIUOZ0HE Fd/t/Q+2Jy+PsIuy5mpLk+z5HpTEbm1kuB9vXAVm0y2y27K2obCIkW4DJicDwVwqH2CG A0iUHZ3YZ7y8fNd0RSzWkV92BHN1ykO4Nefu8rcvZwI+3EFJIRi0pZrsdrcbX+aM1iTC xf8iF4Ly81EF52YDH+fbKwIJIIgChDNX/QK+0sTUG0fH9g0K5cruf7LwrXoGDSrCg0zU LSRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HaWojZ154ty1BuXuO0+YO3eSKuA4lL2H6ORoaKrmkaI=; b=YTbplIPX9t9T4J+OFWjD0EHSCeJ223P0UJhezNAPXhEMT7NTAH1OYB5xy/2/bqDtqo gU5qnU6fpQ2N0TJ+y6Byj78OZN9RDRsMJrhVwxmsEjNWazZ6ucl0/cZM9kL9KhycPhs3 oONDJ4RxooHVa4ulLugyAu0odEVogN/RpuJYRz+rDhgD1a0olegvaypyvawEoajf01UN vTzcmRfxgwGSDUTzjsGtBqbziVx6RwavF671UeBtwlzfXR2fQd0M3WkGtiGQJ0OgOlwu R8MYXYfJA4hb0SG/B0y7P23jutPZqDd5keQgdrMTY5LbENpZlT3luJdPDiZLNVaViExc jHGA==
X-Gm-Message-State: AGi0PuZrnTdMrpOgnuKpgn448MTPBG80j32DlnHzpC4TCi2zmJlja3Rt hgm4Iky4jwfCKHhHVSneWZHFp0bO3D31t50WcH0WqA==
X-Google-Smtp-Source: APiQypIhIT/d5FvU1K0QjMbRnVGxylzeW3doPcc0hM4c3MdSwvAgLYCKVbV2AHXQcPi3pw4+MojrSofdufrNfPlNcBA=
X-Received: by 2002:ab0:4ac9:: with SMTP id t9mr2241797uae.40.1588325825619; Fri, 01 May 2020 02:37:05 -0700 (PDT)
MIME-Version: 1.0
References: <CH2PR00MB06798A6DCC36BD152F324155F5AE0@CH2PR00MB0679.namprd00.prod.outlook.com> <88d7c433-bd4b-456a-bc04-d30ed988fe9f@Spark> <BY5PR00MB0676CBF29BE43390EBB459C4F5AC0@BY5PR00MB0676.namprd00.prod.outlook.com>
In-Reply-To: <BY5PR00MB0676CBF29BE43390EBB459C4F5AC0@BY5PR00MB0676.namprd00.prod.outlook.com>
From: Torsten Lodderstedt <torsten@lodderstedt.net>
Date: Fri, 1 May 2020 11:36:54 +0200
Message-ID: <CAHOkhHFZQ=f1GLiZr0e-gOC4PMUT33Wz7-BaynYw3kRWfeB3OQ@mail.gmail.com>
To: Mike Jones <Michael.Jones=40microsoft.com@dmarc.ietf.org>
Cc: John Bradley <jbradley@yubico.com>, Nat Sakimura <nat@sakimura.org>, oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009fc14705a492ece0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/SQABsd61pIo8L-n39nsM-xzH4Hk>
Subject: Re: [OAUTH-WG] [EXTERNAL] Re: 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 09:37:12 -0000

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. See
> https://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
> 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
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>