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

Torsten Lodderstedt <torsten@lodderstedt.net> Sun, 07 June 2020 07:24 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 5B6B03A09F2 for <oauth@ietfa.amsl.com>; Sun, 7 Jun 2020 00:24:43 -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 umSGoZpff3fX for <oauth@ietfa.amsl.com>; Sun, 7 Jun 2020 00:24:41 -0700 (PDT)
Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (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 5C1E83A09F1 for <oauth@ietf.org>; Sun, 7 Jun 2020 00:24:41 -0700 (PDT)
Received: by mail-ej1-x62c.google.com with SMTP id o15so14690559ejm.12 for <oauth@ietf.org>; Sun, 07 Jun 2020 00:24:41 -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=248zMwXHbxlMeNhIN0hVyiGEn20i4dgy96M6Zy1rE84=; b=GqxqoOw5wnLJrPdS6xQSubnQBH+WkKoIMKcrlMesfbnTdTsrti5Sy7WbrQw9YcBZKN iWbKPBAzF2uh81i75V8r6LOA+WCfC1NhnH5stDck91eJVIB3CMO2+Xnf4oiH+sqdUrde HAIkYbolh+fIb6rVEoeUIwylbfEhyYvwPdOpWs3p0guVjjpq0NGiaXBKrXNIIs5V2KD6 w6TB044aUx0nZVHplkkOPLM9lLcu191Uu+5D0nMuN7gG5jpqV02jLgoxJ7NuPa42V4OU N8/0O2WKQe/qEqdq2Sz6IaATJ+sCNWt6XTLXouDrDoNdKLurxEz3iA1h/anqjs9rXfnd 9xMw==
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=248zMwXHbxlMeNhIN0hVyiGEn20i4dgy96M6Zy1rE84=; b=Do3GZftti9hkgDL6NhfB23OPWIG49tl+4hy5+12IVbv8OaNO5JTsv+p8Nx30aXq214 DdVy+JcbNoi1b5krhCXkoj7jIDQ2oWFXeDvbWEBzWvSL2lzevTVRVnztwUqjlBeT140F qUGazeRty5CWf11ikgfgyDUqesSB3PxAkfHbtUhhGdCa2l6GwJpfI9E/7XCfUNHf1IGi vN4rTieq9EYxoddb4iPppzvMIqSIFeu7v7q6oB8bIWW3z4XTO649+Ve3P47LNPGOJV/F DTeCE8FeTjMIfijJp1WrTeyQ8k3ZM/dCU9uGPKdeCIfN0WAgpVBXMjY1MZHqxTmVaWBJ qfqg==
X-Gm-Message-State: AOAM532rbgslPszBoSpJhdPFchgVhmSaMIfvaUG0n2ifGe0ZMDTFJ4Lw 6dQFY6QC3i39cOF3jZUv4keYYQ==
X-Google-Smtp-Source: ABdhPJw7gcWCefC5mKHFG1n4sEuWQCtq6R+uHHQ6eJjcDSciHcaoulaK33VVidCPYAfhw2tHygoeAA==
X-Received: by 2002:a17:906:6686:: with SMTP id z6mr15566809ejo.258.1591514678178; Sun, 07 Jun 2020 00:24:38 -0700 (PDT)
Received: from ?IPv6:2003:eb:8f18:4cac:595f:7e6:53fe:b837? (p200300eb8f184cac595f07e653feb837.dip0.t-ipconnect.de. [2003:eb:8f18:4cac:595f:7e6:53fe:b837]) by smtp.gmail.com with ESMTPSA id n5sm9374981edq.13.2020.06.07.00.24.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 07 Jun 2020 00:24:37 -0700 (PDT)
Content-Type: multipart/signed; boundary=Apple-Mail-8BC59785-8CFD-43A5-9A21-8EE751B3C9AB; 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 09:24:36 +0200
Message-Id: <19341B4C-BCA9-49A6-ACB1-E9466BE9A1E2@lodderstedt.net>
References: <AE6CAFD2-9A1B-4EEE-8F4F-5A1F94E66779@gmail.com>
Cc: Francis Pouatcha <fpo@adorsys.de>, oauth <oauth@ietf.org>
In-Reply-To: <AE6CAFD2-9A1B-4EEE-8F4F-5A1F94E66779@gmail.com>
To: Nov Matake <matake@gmail.com>
X-Mailer: iPhone Mail (17F75)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/1My55mCGnQistwW1b9h7LBuxMR4>
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 07:24:43 -0000

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
>