Re: [OAUTH-WG] OAuth 2.0 DPoP for the Implicit Flow
Rifaat Shekh-Yusef <rifaat.ietf@gmail.com> Tue, 10 March 2020 10:40 UTC
Return-Path: <rifaat.ietf@gmail.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 B720F3A103D for <oauth@ietfa.amsl.com>; Tue, 10 Mar 2020 03:40:45 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 lZIOSsyIPotB for <oauth@ietfa.amsl.com>; Tue, 10 Mar 2020 03:40:41 -0700 (PDT)
Received: from mail-il1-x136.google.com (mail-il1-x136.google.com [IPv6:2607:f8b0:4864:20::136]) (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 8CD243A104D for <oauth@ietf.org>; Tue, 10 Mar 2020 03:40:41 -0700 (PDT)
Received: by mail-il1-x136.google.com with SMTP id o18so11486017ilg.10 for <oauth@ietf.org>; Tue, 10 Mar 2020 03:40:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SW7q0AEW5T6QpI4ZW35zXJ7ESsdF4loqqxWaEIybZsg=; b=RssPwNI2W5ybFKTKL+Nn8Rl9cNKijHunLf76SRApOZxzzjRXNAZLvpYPOomgPypCd6 EPxqPRibZNcK4PNczDEp98aBYEdmRA8jnboSoH1uoyFvhGRNUMe3FeBpOiwfw5TyVUgN D6XozeuNPeCYvLN9N8OphkI4p8OdRuShkYfwsT7v/zl9ssH81icv4QFByxiVyosgPJle JMYKwwF6u+l58eFdP1Gemo9rZl3xqwybszBzS61XY5smlpGyImaUwjYxKoIfl+hNISJ6 droJAC+8fozQlbPVwqCBoxirOwSC86vws8wbnXLBdN3cev+Ua6vifakgW8CoNJ9J/G0d 66Xw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SW7q0AEW5T6QpI4ZW35zXJ7ESsdF4loqqxWaEIybZsg=; b=IGo+PttjvAWZGbi1+M18lwZKY8uaJ23DgAkp6Gx/H0W/KOAnt3a739VBicBJpcvyRU GL0pQp0rgZh2USGFBCt7n2wToIRPXFGys4BL/KgFj3E6xtPLQlyH2Ux52rF4hPiBMCF3 PGzUFOKzw+4c2Nyg4Fak5EuJXHslr096xb1t+PuYu63hYJ8YnvbGk6/xmyrtZx4125Lu KZzOTCgEtGv+vuvw3GYCwmCjNedWwuVWLLOK7AbcRHEyUIrYQH6AEx9vv9qmEBTXa3Rj zUx+KMpCAWxTV8wv2FXwpDOMuexcT5jKxYKVQyKlqFlf7oxDcUVQFIF/2l15hFEvfA6g y0xQ==
X-Gm-Message-State: ANhLgQ1PMcrKZRDI5iuWc6KieGHlolo6SCuWIz0mijy48zFoxSUsEJEj lbapkao8O79GDiSTu+5svhxTyehs5/zaHurCFwZ7RUAh
X-Google-Smtp-Source: ADFU+vvPTMFKFvgu3bJPRtLnor7hX6LBwtfUO5/yNhHvCd4qyVMYVQKZrl6BYOwJkFbw7SXBE1XZe8NQp8Qz7dAleJc=
X-Received: by 2002:a92:5d8f:: with SMTP id e15mr1307795ilg.255.1583836840645; Tue, 10 Mar 2020 03:40:40 -0700 (PDT)
MIME-Version: 1.0
References: <CH2PR00MB06784BE1BB83918ABC652C7AF5FF0@CH2PR00MB0678.namprd00.prod.outlook.com>
In-Reply-To: <CH2PR00MB06784BE1BB83918ABC652C7AF5FF0@CH2PR00MB0678.namprd00.prod.outlook.com>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Date: Tue, 10 Mar 2020 06:40:30 -0400
Message-ID: <CAGL6ep+tgKaW=-rXCMk_8HXXNGWYT3sN7GRqY=x4VUW=Qzc+sg@mail.gmail.com>
To: Mike Jones <Michael.Jones=40microsoft.com@dmarc.ietf.org>
Cc: "oauth@ietf.org" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000044dab905a07dc07b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/sZOI6V8jvgXLrATSXTdckUVqfHE>
Subject: Re: [OAUTH-WG] OAuth 2.0 DPoP for the Implicit Flow
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: Tue, 10 Mar 2020 10:40:46 -0000
Mike, What was the reason for creating a separate draft for this? Why cannot this be folded into the exiting DPoP draft? Regards, Rifaat On Mon, Mar 9, 2020 at 8:12 PM Mike Jones <Michael.Jones= 40microsoft.com@dmarc.ietf.org> wrote: > As I previously described <https://self-issued.info/?p=1967>, members of > the OAuth working group have developed a simplified approach to providing > application-level proof-of-possession protections for OAuth 2.0 access > tokens and refresh tokens. This approach is called OAuth 2.0 Demonstration > of Proof-of-Possession at the Application Layer (DPoP). Among other > benefits, it does not require a complicated and error-prone procedure for > signing HTTP requests, as some past approaches have. > > > > However, the DPoP specification to date has assumed that the client is > using the OAuth authorization code flow. As promised at the last IETF > meeting, we’ve now published a simple companion specification that > describes how DPoP can be used with the OAuth implicit flow – in which > access tokens are returned directly from the authorization endpoint. The > specification is mercifully brief because very little had to be added to > supplement the existing DPoP spec to enable use of DPoP with the implicit > flow. Thanks to Brian Campbell and John Bradley for whiteboarding this > solution with me. > > > > Finally, in a related development, it was decided during the OAuth virtual > interim meeting today to call for working group adoption of the core DPoP > draft. That’s an important step on the journey towards making it a > standard. > > > > The specification is available at: > > - https://tools.ietf.org/html/draft-jones-oauth-dpop-implicit-00 > > > > An HTML-formatted version is also available at: > > - https://self-issued.info/docs/draft-jones-oauth-dpop-implicit-00.html > > > > -- Mike > > > > P.S. This notice was also posted at https://self-issued.info/?p=2063 and > as @selfissued <https://twitter.com/selfissued>. > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth >
- [OAUTH-WG] OAuth 2.0 DPoP for the Implicit Flow Mike Jones
- Re: [OAUTH-WG] OAuth 2.0 DPoP for the Implicit Fl… Filip Skokan
- Re: [OAUTH-WG] OAuth 2.0 DPoP for the Implicit Fl… Rifaat Shekh-Yusef
- Re: [OAUTH-WG] OAuth 2.0 DPoP for the Implicit Fl… Justin Richer
- Re: [OAUTH-WG] OAuth 2.0 DPoP for the Implicit Fl… Aaron Parecki
- Re: [OAUTH-WG] [EXTERNAL] Re: OAuth 2.0 DPoP for … Mike Jones
- Re: [OAUTH-WG] [EXTERNAL] Re: OAuth 2.0 DPoP for … Mike Jones
- Re: [OAUTH-WG] [EXTERNAL] Re: OAuth 2.0 DPoP for … Brian Campbell