Re: [OAUTH-WG] New Version Notification for draft-fett-oauth-dpop-03.txt

Torsten Lodderstedt <> Sun, 24 November 2019 07:59 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 36369120033 for <>; Sat, 23 Nov 2019 23:59:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id I2Gf2HFQ8W-m for <>; Sat, 23 Nov 2019 23:59:30 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::434]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AA3511200EC for <>; Sat, 23 Nov 2019 23:59:29 -0800 (PST)
Received: by with SMTP id z10so13567466wrs.12 for <>; Sat, 23 Nov 2019 23:59:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=nz4FNhCNjsttbjBK93nSzocpZKjewgn5hUGyDmgWwuI=; b=NuuvQQmgAwYUjhYRg77ax7BdSm+6VM98kq8vf8ai4DhYa/SgzR95ZTOA1Rok5/ku9p T2UvPjSV1unEio3DIdKt3zXY6Az9slnQb9VifERXvlY8kf+Mn6AExUqhGFX04Q6Kbwbp b3p9QNoXUedHcODPe1VGZS3c6OluTWZR9A6p1HWp2Js+ngiqbqeKEFXZOctqz+sOtAZX ZwJxdh2xQkt5NE2o/VdAKQCCZJiUoe32q9op5FmuIHQWTfQLY+QExdipDZdvykmwW2ZV Bma1fMmNUP1HfjM1LP/9I6IgEjzfrD+amNStGl7mpVSA6ToxCc+Xl5p4xSqcvfETO0ln Mnnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=nz4FNhCNjsttbjBK93nSzocpZKjewgn5hUGyDmgWwuI=; b=T1lEjYPekQSBbD0hnnT3aFeCMMwRC/KI8nF1bBK6C0Da7dhgVRAs1FbHIOGXvVWr10 HwoXDIFG+1UoCg4tVf5Qki9JpquGISEp4raUyHAkPEm9/7MrIvhvOwrTzGUHQ4H+TSXb BkUk5kKGJtq7T0fhacQbv+UHONjtzBtOtJ7NdHkXYuwLmVHZCp+l1MRXgW0LE/od9AwM mRET4jkH2TE0oiMR4ige7Fvygh8mJm15WaGd8nL6FHDdw1kctWYBnG+dkP27EtWq10bT ykO+Ttzm1n8gnENNDDgT25NFSd6AHzFuJO0ifqeJeeQye+ZQGbu9i2ywCrO2X2KUBohG 9Vuw==
X-Gm-Message-State: APjAAAVA7D9jS0bte1EB5eJNXqxDF9EnepowjQSlBUfHnDKx7ToB1R6k 6sa8PP7PJaCsuXuy7Y5L0TYedzH/xqQtZOtr
X-Google-Smtp-Source: APXvYqx0mkJYgmXu1FjcLeYehrsQWol/n8IEBHX/xLGJDRLrOMTRWf6Ym8naM944H1vw76W7A9AqIQ==
X-Received: by 2002:adf:dc4b:: with SMTP id m11mr11317859wrj.344.1574582367837; Sat, 23 Nov 2019 23:59:27 -0800 (PST)
Received: from [] ( []) by with ESMTPSA id y11sm5261263wrq.12.2019. (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 23 Nov 2019 23:59:27 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Torsten Lodderstedt <>
Mime-Version: 1.0 (1.0)
Date: Sun, 24 Nov 2019 08:59:26 +0100
Message-Id: <>
References: <>
Cc: Justin Richer <>, oauth <>
In-Reply-To: <>
To: Neil Madden <>
X-Mailer: iPad Mail (17A860)
Archived-At: <>
Subject: Re: [OAUTH-WG] New Version Notification for draft-fett-oauth-dpop-03.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OAUTH WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 24 Nov 2019 07:59:32 -0000

Hi Neil,

I would like to summarize what I believe to have understood is your opinion before commenting:
1) audience restricted access tokens is the way to cope with replay attempts between RSs
2) TLS prevents replay at the same RS

re 1) that works as long as ASs support audience restrictions and the audience restriction is the actual resource server URL, otherwise a staged RS can obtain access tokens audience restricted for a different RS and replay it there
re 2) it seems you look onto that threat from the inside of a TLS connection. Let’s assume the attacker obtains the access tokens at the application layer, e.g. through a log file, referrer header, mix-up, browser history and then sends it through a new TLS connection to the same RS. How does TLS help to detect this replay?

best regards,

> Am 24.11.2019 um 08:40 schrieb Neil Madden <>:
> On 22 Nov 2019, at 13:33, Torsten Lodderstedt <> wrote:
>> Hi Neil,
>>>> On 22. Nov 2019, at 20:50, Neil Madden <> wrote:
>>> Hi Torsten,
>>>> On 22 Nov 2019, at 12:15, Torsten Lodderstedt <> wrote:
>>>> Hi Neil,
>>>>> On 22. Nov 2019, at 18:08, Neil Madden <> wrote:
>>>>> I think the phrase "token replay" is ambiguous. Traditionally it refers to an attacker being able to capture a token (or whole requests) in use and then replay it against the same RS. This is already protected against by the use of normal TLS on the connection between the client and the RS. I think instead you are referring to a malicious/compromised RS replaying the token to a different RS - which has more of the flavour of a man in the middle attack (of the phishing kind).
>>>> I would argue TLS basically prevents leakage and not replay.
>>> It also protects against replay. If you capture TLS-encrypted packets with Wireshark you not only cannot decipher them but also cannot replay them because they include specific anti-replay measures at the record level in the form of unique session keys and record sequence numbers included in the MAC calculations. This is essential to the security of TLS.
>> I understand. I was looking onto TLS from an application perspective, that might explain differing perception.
>>>> The threats we try to cope with can be found in the Security BCP. There are multiple ways access tokens can leak, including referrer headers, mix-up, open redirection, browser history, and all sorts of access token leakage at the resource server
>>>> Please have a look at
>>>> also has an extensive discussion of potential counter measures, including audience restricted access tokens and a conclusion to recommend sender constrained access tokens over other mechanisms.
>>> OK, good - these are threats beyond token replay (at least as I understand that term). It would be good to explicitly add them to the DPoP document motivation.
>>> Note that most of these ways that an access token can leak also apply equally to leak of the DPoP JWT, so the protection afforded by DPoP boils down to how well the restrictions encoded into the JWT prevent it from being reused in this case - e.g., restricting the expiry time, audience, scope, linking it to a specific request (htm/htu) etc. 
>>> Every single one of those restrictions can be equally well encoded as caveats on a macaroon access token without any need for public key signatures or additional tokens and headers.
>>>>> But if that's the case then there are much simpler defences than those proposed in the current draft:
>>>>> 1. Get separate access tokens for each RS with correct audience and scopes. The consensus appears to be that this is hard to do in some cases, hence the draft.
>>>> How many deployments do you know that today are able to issue RS-specific access tokens?
>>>> BTW: how would you identify the RS?
>>>> I agree that would be an alternative and I’m a great fan of such tokens (and used them a lot at Deutsche Telekom) but in my perception this pattern needs still to be established in the market. Moreover, they basically protect from a rough RS (if the URL is used as audience) replaying the token someplace else, but they do not protect from all other kinds of leakage/replay (e.g. log files).
>>> Many services already do this. For example, Google encodes the intended RS into the scopes on GCP ( A client can do a single authorization flow to authorize all the scopes it needs and then use repeated calls to the refresh token endpoint to obtain individual access tokens with subsets of the authorized scopes for each endpoint.
>> And that works at google? How does the client indicate the RS it wants to use the first access token (that is obtains in the course of the code exchange)?
> It doesn’t. The initial access token would be for all scopes and the client simply discards that one (or revokes it if the AS supports revoking individual tokens). 
>>> (I think Brian also mentioned this pattern at OSW, but it might have been somebody else).
>> I know the pattern and we used this at Deutsche Telekom, but I don’t know any other deployment utilising this pattern. In my observation, most people treat access tokens as cookies and use them across RSs. Another reason might be that, before resource indicators, there was no interoperable way to ask for a token for a certain RS.
> I don’t know anybody using DPoP either. The point is that you can do this kind of thing right now, so DPoP needs to have a stronger justification for why this isn’t sufficient.
>>>>> 2. Make the DPoP token be a simple JWT with an "iat" and the origin of the RS. This stops the token being reused elsewhere but the client can reuse it (replay it) for many requests.
>>>>> 3. Issue a macaroon-based access token and the client can add a correct audience and scope restrictions at the point of use.
>>>> Why is this needed if the access token is already audience restricted? Or do you propose this as alternative? 
>>> These are all alternatives. Any one of them prevents the specific attack of replay by the RS to another RS.
>> And which does for replay with the same RS?
> TLS. 
> — Neil