Re: [OAUTH-WG] DPoP - Downgrades, Transitional Rollout & Mixed Token Type Deployments

Nov Matake <matake@gmail.com> Sun, 07 June 2020 11:04 UTC

Return-Path: <matake@gmail.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 5EE823A0D3D for <oauth@ietfa.amsl.com>; Sun, 7 Jun 2020 04:04:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, 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=gmail.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 Ed3LCT_OOsCY for <oauth@ietfa.amsl.com>; Sun, 7 Jun 2020 04:04:50 -0700 (PDT)
Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) (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 1EF723A0D3C for <oauth@ietf.org>; Sun, 7 Jun 2020 04:04:50 -0700 (PDT)
Received: by mail-pj1-x102a.google.com with SMTP id ne5so2080486pjb.5 for <oauth@ietf.org>; Sun, 07 Jun 2020 04:04:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=keJ9llU1fCdYpPI3cenkymWSVu/jeZA08DGfAKB4Meg=; b=OtyzqjE/G3nyCYUjxoN2kBDBnH7UtKZHO+4wHAIo+6v7/dWknWeUecPVP6AYOBJw+S BGUeuiQ9PuZnFkCyBk0rFlkXrs5XdbzSa2CESuNpQAxmFk/+RoLiMie8R5+QCDs3L0MN /QTQnc3LgwGQgi9UOt751SwgNXQQmbtnMhbbJXob3ia5fxg9Nit7qtCbWq+PfiKbEBUC dfjEtKlSD1gQAU4pwbrKbaIVVgK5SpNRzQW4WwCTkkX76mjfddTfSA/bsKkWWaCgxtjm XmkL+/fmTrX+7ATBYy9AOKe1cVnLz+TedmWhnLIVnfA//s/S1mWZzUPYwPqkJg0rKQUM YjaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=keJ9llU1fCdYpPI3cenkymWSVu/jeZA08DGfAKB4Meg=; b=kmnwQiHfeZGpkfUsoCJdWJL8Pi61attxUHMppTqwzXi2gl/kVUtR7YeiSdWRJMra28 CvictkmenFkOd1JAPoxOxQWEfVmbrGFDdI5NQlbDUpEU7EpDnWF+3P5kfCf1+/diKVSv kqkaqpHBjJf3OzdCGdRE7YTyiW2yJgLSv0fJRM5t+a9tpOwuJpbQfYUKKuNuPbpvQJMF Iazt38RBMxtG2dewsZWQAWYkFHgiyOAJGjsQNzTiFanoapZmkjMjhN7wbJaadW1bZFGo OQE3KCjrcOTDbiewZYxqiHH3fTpBfFPPOBPtWHMym6o87XIVGYHZ2gd5Ea3omkIwhPJN +d/g==
X-Gm-Message-State: AOAM531QTKcDRILancxJ27uck6xdhypEunslL2IympP101XrVtSy4T7H vFdxFQHehPwHGJ0JVmP9VTE=
X-Google-Smtp-Source: ABdhPJxXz9AYimswfIWh78k3BTMO88+XXLmAHpO7C387Yk4quP5Oq8VBDuFHiJAi2L/fXG2ompc17w==
X-Received: by 2002:a17:90a:e288:: with SMTP id d8mr12606925pjz.173.1591527887736; Sun, 07 Jun 2020 04:04:47 -0700 (PDT)
Received: from [172.16.80.79] (122x210x153x65.ap122.ftth.ucom.ne.jp. [122.210.153.65]) by smtp.gmail.com with ESMTPSA id z144sm4379810pfc.195.2020.06.07.04.04.45 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 07 Jun 2020 04:04:46 -0700 (PDT)
From: Nov Matake <matake@gmail.com>
Message-Id: <8590F26F-309F-4F84-B99F-2D29353859B5@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_848B1ECC-0AF7-4957-8342-74F1AAD74E34"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Sun, 7 Jun 2020 20:04:43 +0900
In-Reply-To: <19341B4C-BCA9-49A6-ACB1-E9466BE9A1E2@lodderstedt.net>
Cc: Francis Pouatcha <fpo@adorsys.de>, oauth <oauth@ietf.org>
To: Torsten Lodderstedt <torsten@lodderstedt.net>
References: <AE6CAFD2-9A1B-4EEE-8F4F-5A1F94E66779@gmail.com> <19341B4C-BCA9-49A6-ACB1-E9466BE9A1E2@lodderstedt.net>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/mFabIlGLQqTBpq38daZD6X5_7wY>
Subject: Re: [OAUTH-WG] DPoP - Downgrades, Transitional Rollout & Mixed Token Type Deployments
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, 07 Jun 2020 11:04:53 -0000

Since each client instance has at least one key, those are same level of state management.

> 2020/06/07 16:24、Torsten Lodderstedt <torsten@lodderstedt.net>のメールt;のメール:
> 
> There are similarities in this particular use case but I would argue DPoP is more light weight than dynamic client registration, less state management in particular.
> 
>> Am 07.06.2020 um 05:41 schrieb Nov Matake <matake@gmail.com>om>:
>> 
>> DPoP-bound refresh token seems feature duplication with dynamic client registration.
>> 
>>> 2020/06/07 7:57、Francis Pouatcha <fpo=40adorsys.de@dmarc.ietf.org <mailto:fpo=40adorsys.de@dmarc.ietf.org>>のメール:
>>> 
>>> 
>>> > Am 05.06.2020 um 22:17 schrieb George Fletcher <gffletch=40aol.com <http://40aol.com/>@dmarc..ietf.org <http://ietf.org/>>:
>>> > 
>>> > Secondly, I do think we need a way to allow for the refresh_token to be bound while leaving the access_tokens as bearer tokens. This adds useful security without impacting existing RS deployments.
>>> 
>>> +1 that’s a very useful feature_______________________________________________
>>> AFAIK a refresh_token is always bound. What am I missing here?
>>> -- 
>>> Francis Pouatcha
>>> Co-Founder and Technical Lead at adorys
>>> https://adorsys-platform.de/solutions/ <https://adorsys-platform.de/solutions/>_______________________________________________
>>> OAuth mailing list
>>> OAuth@ietf.org <mailto:OAuth@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/oauth
>>