Re: [OAUTH-WG] DPoP and implicit/hybrid flows

Justin Richer <jricher@mit.edu> Fri, 16 July 2021 18:18 UTC

Return-Path: <jricher@mit.edu>
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 9FDD93A3FD8; Fri, 16 Jul 2021 11:18:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.196
X-Spam-Level:
X-Spam-Status: No, score=-4.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 iRnOjbH-PkRD; Fri, 16 Jul 2021 11:18:32 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 8657F3A3FD7; Fri, 16 Jul 2021 11:18:32 -0700 (PDT)
Received: from [192.168.1.49] (static-71-174-62-56.bstnma.fios.verizon.net [71.174.62.56]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 16GIIQtA024869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 16 Jul 2021 14:18:27 -0400
From: Justin Richer <jricher@mit.edu>
Message-Id: <03499E20-EB69-4FAB-A2FA-0DEF8EF82CD9@mit.edu>
Content-Type: multipart/alternative; boundary="Apple-Mail=_13718F9F-BD2A-4AE7-8CB0-40661D2895CE"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Date: Fri, 16 Jul 2021 14:18:26 -0400
In-Reply-To: <CAANoGhJpZDpLTxsnJDNUvbCPnXkQGzAmNTM6-rkft2DTJLRkjA@mail.gmail.com>
Cc: Dmitry Telegin <dmitryt=40backbase.com@dmarc.ietf.org>, IETF oauth WG <oauth@ietf.org>
To: John Bradley <ve7jtb@ve7jtb.com>
References: <CAOtx8DnPvgh56Pw8Q2FrWQsbuT6f-iR0z3xnJHHsRmhmbkiWcg@mail.gmail.com> <6389ABA2-12B1-4F42-A8BB-6C7DE4C7178C@mit.edu> <CAANoGhJpZDpLTxsnJDNUvbCPnXkQGzAmNTM6-rkft2DTJLRkjA@mail.gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/u3kUweaDLlx_XIc0OXq7A0lozpA>
Subject: Re: [OAUTH-WG] DPoP and implicit/hybrid flows
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: Fri, 16 Jul 2021 18:18:39 -0000

Binding the access token is not required for FAL3. FAL has nothing to say about access tokens:

https://pages.nist.gov/800-63-FAQ/#q-c8 <https://pages.nist.gov/800-63-FAQ/#q-c8>

FAL3 is about presenting proof of a key representing the user alongside an assertion representing the user. In OIDC this would mean something like the ID token having a key identifier inside of it and the RP prompting the user for the key. This has nothing to do with access tokens, or even calling an identity API like a UserInfo Endpoint. DPoP doesn’t help with any of that since DPoP is about access tokens.

 — Justin

> On Jul 16, 2021, at 1:18 PM, John Bradley <ve7jtb@ve7jtb.com> wrote:
> 
> Binding the token would be required for OAuth or Connect to meet the SP800-63 FAL3 requirements. 
> 
> Something like DPoP might work.  I don't think DPoP itself should directly add support. 
> 
> I don't know if people really care about FAL3,  unfourtunatly the simple solution of using token-binding seems quite dead in browsers. 
> 
> John B. 
> 
> 
> 
> 
> 
> On Fri, Jul 16, 2021, 12:29 PM Justin Richer <jricher@mit.edu <mailto:jricher@mit.edu>> wrote:
> I personally hope we don’t. JAR already gives us signed requests at the authorization endpoint, though the last piece would be binding the token. 
> 
>  — Justin
> 
> > On Jul 15, 2021, at 6:47 PM, Dmitry Telegin <dmitryt=40backbase.com@dmarc.ietf.org <mailto:40backbase.com@dmarc.ietf.org>> wrote:
> > 
> > Hi,
> > 
> > The DPoP spec currently defines how to obtain a DPoP-bound token via token endpoint invocations (namely, authorization_code and refresh_token grants). But it is also possible to obtain access token prior to code-to-token exchange, via OAuth implicit/hybrid flows.
> > 
> > Do we have any plans to support DPoP in authorization endpoint (in addition to token endpoint) and implicit/hybrid flows? Is yes, what it might look like? a "dpop" request parameter or a "DPoP" header?
> > 
> > Regards,
> > Dmitry
> > _______________________________________________
> > OAuth mailing list
> > OAuth@ietf.org <mailto:OAuth@ietf.org>
> > https://www.ietf.org/mailman/listinfo/oauth <https://www.ietf.org/mailman/listinfo/oauth>
> 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org <mailto:OAuth@ietf.org>
> https://www.ietf.org/mailman/listinfo/oauth <https://www.ietf.org/mailman/listinfo/oauth>