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

Torsten Lodderstedt <torsten@lodderstedt.net> Sun, 07 June 2020 11:26 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 40B123A0D69 for <oauth@ietfa.amsl.com>; Sun, 7 Jun 2020 04:26:02 -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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=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=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 ld7ygk2AXvz2 for <oauth@ietfa.amsl.com>; Sun, 7 Jun 2020 04:26:00 -0700 (PDT)
Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (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 C68653A0D67 for <oauth@ietf.org>; Sun, 7 Jun 2020 04:25:59 -0700 (PDT)
Received: by mail-ej1-x631.google.com with SMTP id x1so15028618ejd.8 for <oauth@ietf.org>; Sun, 07 Jun 2020 04:25:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lodderstedt.net; s=google; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=bebG4GJWylV+cJ5auPuTTp6MnBB8oPv0xckZrV63yTQ=; b=sgZxTtNWzmBLQwrH+DwqZsthpdt4v6BtvF7yPeo1WvqJ0hQ0Z+2c1nh0pgmqtnbfKg sT+Wyt1qvvZ5RPjDaMNduOQWQlnYakp+AO8j3nqLtRHWZhNGcPwF/ZNeCr+5xBQ5mUkg 8V45wZ1L7n96JPMGACVpKajmTI678VicPX7hu0MRdRsEKX34Dmmh4JOoPzmPf6EpTuiV IE1pvoYxUMXp1TcTF9Tsx0djw1ScZaxLvyWZ+oqDo+6kwj+oD46uuqsTqrNjpPmOhdqt KhyISNwAsGkHphspeyH6fohmZEDNQHIKL54DrjYUgeXtaqVJ3HFV1Mb4URkL4r3Ef4TY 6UqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=bebG4GJWylV+cJ5auPuTTp6MnBB8oPv0xckZrV63yTQ=; b=rGk5H0Fk3RffSiP6JxhH547Gyj+gstQP8NkGLw6MP0f0SNPiU4HXq0iWxDFQfQ38jW 4s9j5be75lBfWzHsmfgJefsDg8Fd3xizEgxy5Szp1xAxWFxjo5599iW/65P5W+8jevGs UCoivygx6GZg7JKevzevW7F3hcGsp/RH95vVeLkcusOMIkIeJikxJu2NLIxpLcNdhcG7 5X0y85tQBESsq+nyvViXk0yR7k4p761yNy0VjVSE1BbGQ0Vxzhys4eRXZX0Ud2eiruaj 5ssrCFpjF4sllPSPRMsPAYHFf/Vr66wezyA6HqQYtdX2F/mUZGIu+eDQRorhHkIdTU5o HK6A==
X-Gm-Message-State: AOAM531Lmq6gwxkKnzbjnAOEq+sgSl4YOukdtenSBXyU1XcSpb89FBDs NKXyKjS5BZNEj83RD2KXPDmTxA==
X-Google-Smtp-Source: ABdhPJw2WelTT7nZmDIRi6/JLwygEIAtP/AaqBiUaUEQBqeKO4Zm7eub06hBd5gKrn62tQtdkDAuIw==
X-Received: by 2002:a17:906:6897:: with SMTP id n23mr16946926ejr.437.1591529158149; Sun, 07 Jun 2020 04:25:58 -0700 (PDT)
Received: from ?IPv6:2a01:598:8184:992b:6522:fbe:7df4:6df6? ([2a01:598:8184:992b:6522:fbe:7df4:6df6]) by smtp.gmail.com with ESMTPSA id t12sm8272037eje.21.2020.06.07.04.25.56 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 07 Jun 2020 04:25:57 -0700 (PDT)
Content-Type: multipart/signed; boundary=Apple-Mail-FB7CC23C-1123-4AE7-8AF0-AB40DE91872C; protocol="application/pkcs7-signature"; micalg=sha-256
Content-Transfer-Encoding: 7bit
From: Torsten Lodderstedt <torsten@lodderstedt.net>
Mime-Version: 1.0 (1.0)
Date: Sun, 7 Jun 2020 13:25:54 +0200
Message-Id: <1ABEEE6B-761E-458B-937D-F3581BC6DE55@lodderstedt.net>
References: <8590F26F-309F-4F84-B99F-2D29353859B5@gmail.com>
Cc: Francis Pouatcha <fpo@adorsys.de>, oauth <oauth@ietf.org>
In-Reply-To: <8590F26F-309F-4F84-B99F-2D29353859B5@gmail.com>
To: Nov Matake <matake@gmail.com>
X-Mailer: iPhone Mail (17F75)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/yv__qDiGJIjcab7R6ZQ8BkLlI84>
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:26:02 -0000

If the client would register for every transaction.

And don’t forget, DPoP also supports sender constrained access to resource servers, which dyn registration does not.

> Am 07.06.2020 um 13:04 schrieb Nov Matake <matake@gmail.com>om>:
> 
> 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>のメールt;のメール:
>>>> 
>>>>> 
>>>>> > Am 05.06.2020 um 22:17 schrieb George Fletcher <gffletch=40aol.com@dmarc..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/
>>>> _______________________________________________
>>>> OAuth mailing list
>>>> OAuth@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/oauth
>>> 
>