Re: [OAUTH-WG] Second WGLC on "JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens"

Aaron Parecki <aaron@parecki.com> Thu, 16 April 2020 20:14 UTC

Return-Path: <aaron@parecki.com>
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 99FBB3A0FC7 for <oauth@ietfa.amsl.com>; Thu, 16 Apr 2020 13:14:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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=parecki-com.20150623.gappssmtp.com
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 v14cuLf-JlEP for <oauth@ietfa.amsl.com>; Thu, 16 Apr 2020 13:14:05 -0700 (PDT)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (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 5A4F33A0F9B for <oauth@ietf.org>; Thu, 16 Apr 2020 13:14:05 -0700 (PDT)
Received: by mail-io1-xd2e.google.com with SMTP id 19so6585931ioz.10 for <oauth@ietf.org>; Thu, 16 Apr 2020 13:14:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parecki-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4n2f8OWKgi9e06ssTmkN7EAN+bv2YTeSMxPsAMRdSSI=; b=ZfGD7gjWAjy3abnyJzEn7xkPMEh1q0X6sb7fFDtuzMX653OkvrI6pRPnyw4RDS6Y6i M2mxROzxllcYJrQAp0p7Oz9PDhm95ygY/wXP6y7Sb7T4er9aEm+27Yfe6XhmtPbd35pi +jxLEt3O6fG2/NE5NHDG3AlhGaXcNntVRyVgvV1rXRKICeWAi7m7i4g6IlFYO7g7vdvP QLSbguDL5coun40TtEj22OyaO6osB910YI3i0S/9+EbjdJrIisWhuQgFzXWOD2fD9FRR udg8baX9/lr6QYh6xi0rSvmCCuTeBVwLgLR6YeeNsYAnY9vsyN6MOBEFzvgZxknktfNe 4IHA==
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=4n2f8OWKgi9e06ssTmkN7EAN+bv2YTeSMxPsAMRdSSI=; b=JCoMnkV5l9k37glmj2JPB0j++bWndzBaoAbNaI+yq7M8OsR97qeBbYyODBQ4maygcR m7oqSpHb7URb+8jxiaF8YM9q3q8mcDdpkd8b7OSIwMRS7oENQ2DP/rXMMbETGbA1kine d+aIFmIXi4H8q1GKpVWPNk3+pp5x3oNx2Xjjzov4z2+PeVhK2Od4GRtPIy0ZQUqUaqEd /a2bhpT2JZbszkkVweE6eFnWfQeB9eykgHsMtfqoNtcGfnK2opYqBod/GTePkIknmXg3 Q9007FOc99qMzaRqiZyKKujx14+oiXuaYKGH7vQzy4UUZfcIZSGPqFS9aJXFLYhnkGRx W+6g==
X-Gm-Message-State: AGi0PuY5kYQrJjg4U2oVGzBOxgg0baWhRUkPGKBdhKX6M44m3xafxbEm RF8GVrnFoaj61vzVOP71MRiGm8BXx2U=
X-Google-Smtp-Source: APiQypK0MPUQe4eIWT605+n1lGKoYnSTBN6UIlez9MHr9wyz1/6OQHuROj8nTKunOF/eEBEwKaqkow==
X-Received: by 2002:a02:a68e:: with SMTP id j14mr67084jam.86.1587068043639; Thu, 16 Apr 2020 13:14:03 -0700 (PDT)
Received: from mail-io1-f44.google.com (mail-io1-f44.google.com. [209.85.166.44]) by smtp.gmail.com with ESMTPSA id x15sm7376637ilg.29.2020.04.16.13.14.02 for <oauth@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 16 Apr 2020 13:14:02 -0700 (PDT)
Received: by mail-io1-f44.google.com with SMTP id n10so22460787iom.3 for <oauth@ietf.org>; Thu, 16 Apr 2020 13:14:02 -0700 (PDT)
X-Received: by 2002:a6b:7f07:: with SMTP id l7mr12595900ioq.14.1587068042329; Thu, 16 Apr 2020 13:14:02 -0700 (PDT)
MIME-Version: 1.0
References: <CAGL6epKuHTqLrZEjm0goKV+3jaPfTkN_JSLc0jfQyPqNzeP3aA@mail.gmail.com> <CAGBSGjpBqeHxFNJ7OEXZwYQb=SG6ian=zpoNHezQ_OYwFNZNBw@mail.gmail.com> <CA+k3eCQGgnSGAcNP4KJik9riWYdRTpSOV-sgZHXMCJUWhh5U5w@mail.gmail.com>
In-Reply-To: <CA+k3eCQGgnSGAcNP4KJik9riWYdRTpSOV-sgZHXMCJUWhh5U5w@mail.gmail.com>
From: Aaron Parecki <aaron@parecki.com>
Date: Thu, 16 Apr 2020 13:13:51 -0700
X-Gmail-Original-Message-ID: <CAGBSGjopPrTjoKxgkyV3=WwUAn8=hwWkczCPHsJtAd-2wr1ePw@mail.gmail.com>
Message-ID: <CAGBSGjopPrTjoKxgkyV3=WwUAn8=hwWkczCPHsJtAd-2wr1ePw@mail.gmail.com>
To: Brian Campbell <bcampbell@pingidentity.com>
Cc: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>, oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e5c55d05a36e12d7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/TM8BuESpbM3kqQTvkg-nkp9GA6o>
Subject: Re: [OAUTH-WG] Second WGLC on "JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens"
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: Thu, 16 Apr 2020 20:14:08 -0000

My mistake! In that case, my request is editorial, to mention that in
section 2.1 where it first talks about signing algorithms.

----
Aaron Parecki
aaronparecki.com
@aaronpk <http://twitter.com/aaronpk>



On Thu, Apr 16, 2020 at 1:12 PM Brian Campbell <bcampbell@pingidentity.com>
wrote:

> sec 4 does have "The resource server MUST reject any JWT in which the
> value of "alg" is "none".'
>
> On Thu, Apr 16, 2020 at 1:09 PM Aaron Parecki <aaron@parecki.com> wrote:
>
>> Section 2.1 says:
>>
>> > Although JWT access tokens can use any signing algorithm, use of
>> > asymmetric algorithms is RECOMMENDED
>>
>> Can this be strengthened to disallow the `none` algorithm? Something like
>> adding "... and MUST NOT use the "none" algorithm".
>>
>> Given that the JWT BCP doesn't disallow the "none" algorithm, technically
>> someone could follow both this JWT Access Token spec and the JWT BCP spec
>> and end up with an implementation that allows an AS to accept JWTs with the
>> "none" algorithm.
>>
>> ----
>> Aaron Parecki
>> aaronparecki.com
>> @aaronpk <http://twitter..com/aaronpk>
>>
>>
>>
>> On Wed, Apr 15, 2020 at 11:59 AM Rifaat Shekh-Yusef <
>> rifaat.ietf@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>>
>>>
>>> This is a second working group last call for "JSON Web Token (JWT)
>>> Profile for OAuth 2.0 Access Tokens".
>>>
>>>
>>>
>>> Here is the document:
>>>
>>> https://tools.ietf.org/html/draft-ietf-oauth-access-token-jwt-06
>>>
>>>
>>>
>>> Please send your comments to the OAuth mailing list by April 29, 2020.
>>>
>>>
>>>
>>> Regards,
>>>
>>>  Rifaat & Hannes
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>
> *CONFIDENTIALITY NOTICE: This email may contain confidential and
> privileged material for the sole use of the intended recipient(s). Any
> review, use, distribution or disclosure by others is strictly prohibited.
> If you have received this communication in error, please notify the sender
> immediately by e-mail and delete the message and any file attachments from
> your computer. Thank you.*