IETF Logo Mail Archive

Re: [OAUTH-WG] Stephen Farrell's Discuss on draft-ietf-oauth-json-web-token-27: (with DISCUSS and COMMENT)

Carsten Bormann <cabo@tzi.org> Mon, 03 August 2020 14:42 UTC

Return-Path: <cabo@tzi.org>
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 EE97A3A0B79 for <oauth@ietfa.amsl.com>; Mon, 3 Aug 2020 07:42:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 FVBpZk22js9F for <oauth@ietfa.amsl.com>; Mon, 3 Aug 2020 07:42:10 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 106B83A0B51 for <oauth@ietf.org>; Mon, 3 Aug 2020 07:42:09 -0700 (PDT)
Received: from [172.16.42.101] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4BL0w00bqhz17qv; Mon, 3 Aug 2020 16:42:08 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739439BAF0C2A@TK5EX14MBXC286.redmond.corp.microsoft.com>
Date: Mon, 03 Aug 2020 16:42:06 +0200
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "oauth@ietf.org" <oauth@ietf.org>
X-Mao-Original-Outgoing-Id: 618158526.810256-afc169bc568f7e8545bf4e589f6ebb9f
Content-Transfer-Encoding: quoted-printable
Message-Id: <6A795E47-860D-4A1C-89B6-565937BEEFC7@tzi.org>
References: <20141002120308.9386.79961.idtracker@ietfa.amsl.com> <4E1F6AAD24975D4BA5B16804296739439BAF0C2A@TK5EX14MBXC286.redmond.corp.microsoft.com>
To: Mike Jones <Michael.Jones@microsoft.com>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/3X_TmjWQLpTcBuPiBhIt0u7Hros>
Subject: Re: [OAUTH-WG] Stephen Farrell's Discuss on draft-ietf-oauth-json-web-token-27: (with DISCUSS and COMMENT)
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: Mon, 03 Aug 2020 14:42:17 -0000

On 2014-10-06, at 09:54, Mike Jones <Michael.Jones@microsoft.com> wrote:

>> - 4.1.7: maybe worth adding that jti+iss being unique enough is not sufficient and
>> jti alone has to meet that need. In
>> X.509 the issuer/serial has the equivalent property so someone might assume
>> sequential jti values starting at 0 are ok.
> 
> Makes sense to add a warning of some kind along these lines.  I think I know the reasons you say that, but can you expand on that thought a bit before I take a stab on writing this up?  For instance, while normally true, I don't think your observation is true if a relying party will only accept tokens from a single issuer.

So can someone remind me why jti needs to be unique globally, and not just per issuer?

Grüße, Carsten

v2.23.0 | Report a Bug | By Email