IETF Logo Mail Archive

Re: [OAUTH-WG] New OAuth DPoP and Security BCP drafts

Sascha Preibisch <saschapreibisch@gmail.com> Thu, 01 August 2019 20:44 UTC

Return-Path: <saschapreibisch@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 781BA12022B for <oauth@ietfa.amsl.com>; Thu, 1 Aug 2019 13:44:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
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, FREEMAIL_FROM=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: 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 1d50pTmMmpJ7 for <oauth@ietfa.amsl.com>; Thu, 1 Aug 2019 13:44:29 -0700 (PDT)
Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (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 119E41201BB for <oauth@ietf.org>; Thu, 1 Aug 2019 13:44:29 -0700 (PDT)
Received: by mail-wm1-x32e.google.com with SMTP id f17so64330409wme.2 for <oauth@ietf.org>; Thu, 01 Aug 2019 13:44:28 -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=EquOcKkggtw8hcRgdL4cGqqlVKGtIKp2raEh4WtjYQs=; b=RWYp/bg2N11YZ2SmrSsuZUmev9PxXIa2osv1R5HPVD0fNlP2RtZIO3Nh2iiHahmBg0 jI6kRWdFUxPRcvyLdyKoVo4qMxE0Mzm3hULnzWOhskUFXMMoTXZUxX5uslKcTAQpVIns 1AZSp5Vyu3MdszUHy5RZ0wupGODJe/ONRdKWKK8ladP5I64bXzynkDtVa1r5y0vOYx54 1ArWpMq1eFqjfUL411ffbekPLH3LQPxkyY0tvU+RBqsBEMlKbDynFnqlcVWfo86jNbNL WQHIUCjttqQEluxJyNfxnzf/2P2vc/QfBZC+isDHzzY2wp8fJ0JtnSWqwcTSQbCoRve2 JDlA==
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=EquOcKkggtw8hcRgdL4cGqqlVKGtIKp2raEh4WtjYQs=; b=G7qLOOkDhbeGg42VOG3mw/5oVuUrnQBuGTTI5SJX64WBTEdiGGzXyae6tzwl9y7i79 eaXlFGG06giXms1fHPh3OJgm0+J9TnlpUTAE/yrer5fBGa1rKDLuT0mUUIdHOGuQiuEz 4zJ62tZ8S52T0p9SPDOHDgEF9zPZfoQ1zDgxBcjWbGrunMGl8++v+bx8DP4/C083RuhE mB4OQZ2CkdUwds3aaALSPet3QtmSyILWobz3ZtoFekyKGAuat0Rd9l97Bc2nkcgUSTqB rE1imM0JvoTrzD0hbZcC523PIxwJEH0B/SPaoyOp/9Grj9JNm2jSpooHcx9iBDrdM5T1 zo4Q==
X-Gm-Message-State: APjAAAVE9srlz8AKFQgt/AChYC/VUOKrUycaiRkNt07g310yLwdBWt4+ dY7ZTE+ia5zNV0jUxqscem12D6J2pDZS4Ig1s2A=
X-Google-Smtp-Source: APXvYqx7xeTtERz2wWCZUraeIv4oaqyHuWKdjH9UrKTitZ5ntqqJRhDco8K4LrBbCB1ueHRWKoyUoZegLt8rp7lWbUo=
X-Received: by 2002:a05:600c:204c:: with SMTP id p12mr388364wmg.121.1564692267448; Thu, 01 Aug 2019 13:44:27 -0700 (PDT)
MIME-Version: 1.0
References: <CAHB17EwniJw9R3Cr9d_AZjaepha+UO+eBBLHYdOZNUEyt+c2Xw@mail.gmail.com>
In-Reply-To: <CAHB17EwniJw9R3Cr9d_AZjaepha+UO+eBBLHYdOZNUEyt+c2Xw@mail.gmail.com>
From: Sascha Preibisch <saschapreibisch@gmail.com>
Date: Thu, 01 Aug 2019 13:43:37 -0700
Message-ID: <CAP=vD9v5FczqKihQZ=4aZXOyUn34RgVUcuJ=VfeE8Du2uHHffA@mail.gmail.com>
To: Daniel Fett <danielf+oauth@yes.com>
Cc: IETF oauth WG <oauth@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/BeK6PwIszDqwoKuY3vDT_qzdIHg>
Subject: Re: [OAUTH-WG] New OAuth DPoP and Security BCP drafts
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: Thu, 01 Aug 2019 20:44:32 -0000

Hi all!

I am reading through the latest draft ( ... dpop-02). When I got to
the first example request (bullet 5.) I saw that only 'grant_type,
code, redirect_uri' are used.

If I am not mistaken the recommendation is to generally use PKCE with
an authorization_code flow. Therefore, I wondered if the example
should also include a 'code_verifier'.

Thanks,
Sascha

On Mon, 8 Jul 2019 at 06:30, Daniel Fett <danielf+oauth@yes.com> wrote:
>
> All,
>
> In preparation for the meeting in Montreal, I just uploaded a new version of the DPoP draft:
> https://tools.ietf.org/html/draft-fett-oauth-dpop-02
>
> Please have a look and let me know what you think. We should make this a working group item soon.
>
> As you might have noticed, there is also a new version of the Security Best Current Practice draft:
> https://tools.ietf.org/html/draft-ietf-oauth-security-topics-13
>
> -Daniel
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email