IETF Logo Mail Archive

Re: [OAUTH-WG] draft-fett-oauth-dpop-00

Phil Hunt <phil.hunt@oracle.com> Mon, 08 April 2019 23:23 UTC

Return-Path: <phil.hunt@oracle.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 1BF92120125 for <oauth@ietfa.amsl.com>; Mon, 8 Apr 2019 16:23:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.311
X-Spam-Level:
X-Spam-Status: No, score=-2.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oracle.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 UW27e2HbM1Ts for <oauth@ietfa.amsl.com>; Mon, 8 Apr 2019 16:23:42 -0700 (PDT)
Received: from userp2130.oracle.com (userp2130.oracle.com [156.151.31.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0B6F120123 for <oauth@ietf.org>; Mon, 8 Apr 2019 16:23:42 -0700 (PDT)
Received: from pps.filterd (userp2130.oracle.com [127.0.0.1]) by userp2130.oracle.com (8.16.0.27/8.16.0.27) with SMTP id x38NIssV171500; Mon, 8 Apr 2019 23:23:41 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=content-type : mime-version : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=corp-2018-07-02; bh=bPK9DmV9d1D8ruis/Blh63VK+N3VC3fgJC5AOGV0QQ8=; b=AgO+iPAuucOF3ALjoA9jKI4Aa8kbneix4QJRlMVCZb/GjpDZb7KdcHS4HQPdS46SYhV7 knV1J0G1LivyOwLZjGEWUbNtsv0Nwyp3oRW+2QkV6FKofj6WXbj6qfZOlAN5yt3qo8qm YCQqnV0aokUK8HG1ke+TlWW/qbpitBbZo02Ue0i6fz2cicS6tEhkzf9d0bTg9hSrCPKR 4y8KplAA6vEM3eqJJDkoh9e0jmRBs+gQPeztbAf6DZtHffHyftSL1DGnEEgvqjeGgGAi PMX4Qv+MaBisRL8bp7XgQuausUGacqJDl/H9TS15k3sEX5Ge1Cf1oaAvOC3EUhGyK1UM 1Q==
Received: from aserp3030.oracle.com (aserp3030.oracle.com [141.146.126.71]) by userp2130.oracle.com with ESMTP id 2rpkhssmq2-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 08 Apr 2019 23:23:40 +0000
Received: from pps.filterd (aserp3030.oracle.com [127.0.0.1]) by aserp3030.oracle.com (8.16.0.27/8.16.0.27) with SMTP id x38NNWgR095873; Mon, 8 Apr 2019 23:23:40 GMT
Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by aserp3030.oracle.com with ESMTP id 2rpj5a8dyb-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 08 Apr 2019 23:23:39 +0000
Received: from abhmp0014.oracle.com (abhmp0014.oracle.com [141.146.116.20]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id x38NNcY2009474; Mon, 8 Apr 2019 23:23:38 GMT
Received: from [192.168.1.22] (/70.70.142.148) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 08 Apr 2019 16:23:38 -0700
Content-Type: multipart/alternative; boundary="Apple-Mail-71357F0F-E2AC-452F-B98D-73B14906330C"
Mime-Version: 1.0 (1.0)
From: Phil Hunt <phil.hunt@oracle.com>
X-Mailer: iPhone Mail (16D57)
In-Reply-To: <458bb5b9-f31f-4564-ae13-bc9f17a3fa4a@aol.com>
Date: Mon, 08 Apr 2019 16:23:36 -0700
Cc: Daniel Fett <danielf+oauth@yes.com>, oauth@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <62C502BF-326F-4849-A1D2-A59B190FF200@oracle.com>
References: <0a9af6f6-1b5d-244d-06af-9d14461b1d69@yes.com> <4c849a55-013c-c606-8877-ae39a6ab79ff@aol.com> <435a1adb-6293-8745-96e8-d608f7dd934f@yes.com> <458bb5b9-f31f-4564-ae13-bc9f17a3fa4a@aol.com>
To: George Fletcher <gffletch=40aol.com@dmarc.ietf.org>
X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=9221 signatures=668685
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904080168
X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=9221 signatures=668685
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904080168
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/2ynFbbTbFD2j1tuobMsTflsCYdc>
Subject: Re: [OAUTH-WG] draft-fett-oauth-dpop-00
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, 08 Apr 2019 23:23:45 -0000

Question. One of the issues that Justin Richer’s signing draft tried to address was url modification by tls terminators/load balencers/proxies/api gateways etc. 

How do you see this issue in dpop? Is it a problem? 

Phil

> On Apr 3, 2019, at 9:01 AM, George Fletcher <gffletch=40aol.com@dmarc.ietf.org> wrote:
> 
> Perfect! Thank you! A couple comments on version 01...
> 
>    POST /token HTTP/1.1
>    Host: server.example.com
>    Content-Type: application/x-www-form-urlencoded;charset=UTF-8
>    DPoP-Binding: eyJhbGciOiJSU0ExXzUi ...
> 
>    grant_type=authorization_code
>    &code=SplxlOBeZQQYbYS6WxSbIA
>    &redirect_uri=https%3A%2F%2Fclient%2Eexample%2Ecom%2Fcb
>    (remainder of JWK omitted for brevity)
> 
> I believe the "(remainder of JWK..." should be moved to the DPoP-Binding header...
> 
> Also, there is no discussion of the DPoP-Binding header outside of the token request, but I suspect that is the desired way to communicate the DPoP-Proof to the RS.
> 
> Possibly an example in the session for presenting the token to the RS would help.
> 
> Thanks,
> George
> 
>> On 4/3/19 11:39 AM, Daniel Fett wrote:
>> This is fixed in -01:
>> 
>> https://tools.ietf.org/html/draft-fett-oauth-dpop-01
>> 
>> -Daniel
>> 
>>> Am 03.04.19 um 17:28 schrieb George Fletcher:
>>> A quick question regarding...
>>> 
>>>    o  "http_uri": The HTTP URI used for the request, without query and
>>>       fragment parts (REQUIRED).
>>> 
>>> Is 'without' supposed to be 'with' ? The example shows the http_uri *with* the query parameters :)
>>> 
>>>> On 3/28/19 6:17 AM, Daniel Fett wrote:
>>>> Hi all,
>>>> 
>>>> I published the first version of the DPoP draft at https://tools.ietf.org/html/draft-fett-oauth-dpop-00
>>>> 
>>>> Abstract
>>>> 
>>>>    This document defines a sender-constraint mechanism for OAuth 2.0
>>>>    access tokens and refresh tokens utilizing an application-level
>>>>    proof-of-possession mechanism based on public/private key pairs.
>>>> 
>>>> Thanks for the feedback I received so far from John, Mike, Torsten, and others during today's session or before!
>>>> 
>>>> If you find any errors I would welcome if you open an issue in the GitHub repository at https://github.com/webhamster/draft-dpop
>>>> 
>>>> - Daniel    
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> OAuth mailing list
>>>> OAuth@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/oauth
>>> 
>> 
> 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_oauth&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=na5FVzBTWmanqWNy4DpctyXPpuYqPkAI1aLcLN4KZNA&m=eQpusEFY7fROXNfEJmh0QzkejgdgaVnILpbm2q8x9II&s=8LDvfTYESi1fDeRK7mQrHFeo9okoJ4NTZU4OHyeRJWk&e=

v2.23.0 | Report a Bug | By Email