IETF Logo Mail Archive

Re: [OAUTH-WG] OAuth 2.1 - require PKCE?

Dick Hardt <dick.hardt@gmail.com> Fri, 08 May 2020 19:49 UTC

Return-Path: <dick.hardt@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 90F473A0E09 for <oauth@ietfa.amsl.com>; Fri, 8 May 2020 12:49:08 -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=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 dtBUVzoDb4BX for <oauth@ietfa.amsl.com>; Fri, 8 May 2020 12:49:03 -0700 (PDT)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 583753A0C1C for <oauth@ietf.org>; Fri, 8 May 2020 12:49:03 -0700 (PDT)
Received: by mail-lf1-x12e.google.com with SMTP id s9so2374778lfp.1 for <oauth@ietf.org>; Fri, 08 May 2020 12:49:03 -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=N7Kpet99hAkJC3xO+huHDbjQMqDWToH4tnX0rF7UUeM=; b=Xmoc+OobzonQmXRa7gDhccFuZqvt0N7J3ZLd0QlLvSwM7VYXIsVR/wSmX6r5O312hD Zh3wy//H9ZgmH2zqSioGMCAz7LClCrtOT5BYLySnRh02QHjgY9RkniEDODP+47Ft6B8y awGLl6r37v4rwReYX4kdoML/8GLa3NK+xdC+fT9y3b3q2WtqjmSG5QX5ts0pQjKN3iUQ +MmfE/6h9FeOrgUswZ+cBB3CNkftG7qAwzD7nPZzHD0WCmAEO4g22Ui4XS0lHSG2fVsj +aN5TUDHTw6rdsTPjPJWDrZjNpFukiWnxJsoiGpAsW7YLrkaUekQiB173NKSgAcbuwGc n8LA==
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=N7Kpet99hAkJC3xO+huHDbjQMqDWToH4tnX0rF7UUeM=; b=noDgZMo+jYPu6yzLFrZUDjghIogzY17pOrxjU67/bORi5+C1UxP75Wc75ZxnkSdW3s XAEbovTJ+KgWMEgiUs3XH+OQ5F75RQvxHmO6P2QbiQ+xfCDzmspcWGyQjiGnycj5wH43 PKoojxruVXQSB35BIElGcxc8X6mXT++XFReukwZstg+B5yhjC70SaMLhgWzcs4ycqlKE 6/MdfW3NAG5Y1lzl9QyKrWVZaXWslx6lTgk/TPHRDGY/Y6rqdS1w4NjLNAw2/fVx1CxM lqbl5K/w6sWhT7fn2rebVAJRA0M0X0I0tCj3wRBaXJnZGY42KFBnHuJa/ItlvzTB/fta dHCA==
X-Gm-Message-State: AOAM531dMq6vMLCp0vGn16PTq0cheBEdld7SeJJ9BrFBG7Y7sLDd99op TEvKRp23ehoeG1k9qC7hyDO32J3l0EEKgKsdXSskteHX
X-Google-Smtp-Source: ABdhPJwOuwsFQGRWglAoR4J7BTA9NzJ5SMRe5JQrtTQ6sUBcp++Jdctba8Yu6/hfsNe06KcLewY6ew88JJZ3ggzsOFY=
X-Received: by 2002:a19:80ca:: with SMTP id b193mr2601366lfd.7.1588967341293; Fri, 08 May 2020 12:49:01 -0700 (PDT)
MIME-Version: 1.0
References: <BY5PR00MB06766F71775C01E586CD1C12F5A20@BY5PR00MB0676.namprd00.prod.outlook.com> <A16DE3EC-26C8-4D0A-8592-5703159367E0@pragmaticwebsecurity.com> <CAD9ie-vosKtF2jSLtZSKk4E2-6BEOGZzvzNeH=HQy2L6DCuonw@mail.gmail.com> <CAGBSGjp7SKiyD5DFYFb3kQXxpnL8cU7UObDTg2J+CL_FJaK7ew@mail.gmail.com>
In-Reply-To: <CAGBSGjp7SKiyD5DFYFb3kQXxpnL8cU7UObDTg2J+CL_FJaK7ew@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Fri, 08 May 2020 12:48:35 -0700
Message-ID: <CAD9ie-uKhqECOaE-+Vtx2kK3wNN4iUZ-vcSus3+mbL3VNWMPAw@mail.gmail.com>
To: Aaron Parecki <aaron@parecki.com>
Cc: Philippe De Ryck <philippe@pragmaticwebsecurity.com>, Mike Jones <Michael.Jones=40microsoft.com@dmarc.ietf.org>, OAuth WG <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f003ac05a5284955"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/Gd8V0JZ9wepOrNnznw2uZAo_DsM>
Subject: Re: [OAUTH-WG] OAuth 2.1 - require PKCE?
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, 08 May 2020 19:49:10 -0000

On Fri, May 8, 2020 at 12:42 PM Aaron Parecki <aaron@parecki.com> wrote:

> > FYI: An objective of OAuth 2.1 is not to introduce anything new -- it is
> OAuth 2.0 with best practices.
>
> The line there is kind of fuzzy. The objective is not to introduce new
> concepts, however there are some changes defined that are "breaking
> changes" from plain OAuth 2.0, because those things being removed were not
> best practices for example.
>

I was clarifying that OAuth 2.1 is not introducing new features, for eg.
the WebSocket support question.

I think we can say that:

An OAuth 2.0 compliant deployment following "best practices" is also an
OAuth 2.1 compliant deployment.

This thread is a discussion of what "best practices" is.

v2.23.0 | Report a Bug | By Email