IETF Logo Mail Archive

Re: [OAUTH-WG] [EXTERNAL] OAuth 2.1: dropping password grant

Dick Hardt <dick.hardt@gmail.com> Wed, 19 February 2020 19:35 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 41871120018 for <oauth@ietfa.amsl.com>; Wed, 19 Feb 2020 11:35:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 P_rH6TTpZodu for <oauth@ietfa.amsl.com>; Wed, 19 Feb 2020 11:35:32 -0800 (PST)
Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (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 851D5120112 for <oauth@ietf.org>; Wed, 19 Feb 2020 11:35:31 -0800 (PST)
Received: by mail-lj1-x22e.google.com with SMTP id q8so1589438ljj.11 for <oauth@ietf.org>; Wed, 19 Feb 2020 11:35:31 -0800 (PST)
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=YFVtBkd9jHrn8SAxDypp3/Fk6kifAu8opamvBiE3JvE=; b=FGWBkbFcHiaGS6yk+2UI7ZLoXy+VXjIqf06FCsLIGxPZIruP/JmZmLq2M8Y2UlFE12 bnQrSIigijNMANeCzJREqz64Qq/Aqn+jgjIdlur01bZQYMOiAs/noq55qCoFKWQ64dUz 2fu9YR9TeQsWQ52dXzZiqwxNXsEPHO/NIYv8mAE5NqiAiCuQA1/zCIj18eME4UT2yCvC JMtDakb2pSEvpMc01tcZT5i9ZYNvOQMGERjV1gIJR2OlsgoQwx4deU/o4uUOmQB0kLdD DfC/3lSRpQvtIw0MpS9D7I6yvrQ5J9dYMpNgmYIgvZGUmriYoxpOekoRi5XbtPoEpUUq u6wA==
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=YFVtBkd9jHrn8SAxDypp3/Fk6kifAu8opamvBiE3JvE=; b=YbueIGbpq71QP3voTveJfu1Xi5a0bExawRFgpGDD7TiG64zldsV3sHWF+zzC7X0FAH lhjW8zCQEQqN4P6tjXLZ7sIyZrkEkB/3xUDd0JqZkTKGgdsWLEbXaSeERgV3dwjMAJv+ 4+tUzp1cVi2+27YRQ5C6+cHxIHU9mHOUsgDPmCz3mAM6w4FPc0mxyrj+/eA30utS4fLG O3EeWB4EEhW831vtLBmP/YoVYbJ1RTkRdJxnd4nht5FkwgE77QtZTJU+mtzpJirMnYvi lsyMmLmxWPcUTpEERGQXu4QU8zldvGmf3/NnMr6uyisi4/tdcK7ZJZS2I9/45wSJmtrf aC3Q==
X-Gm-Message-State: APjAAAUQ/Buo7EpHmYyMQQWX7rnodDRDhWVZugwF1paE6777O6loqNEg 88b445mSi8OVqM7BDRpr5bNJcAf/q4W95TLKd0c=
X-Google-Smtp-Source: APXvYqxIr/7wicuY0zpDR3+1HCrp3065W9D/9IaGLHeRKsnt09ZdZG8yc5fiPeFHplMvjMnIeBaiMjlMaQ4I9nH5/uE=
X-Received: by 2002:a2e:865a:: with SMTP id i26mr17055136ljj.236.1582140929546; Wed, 19 Feb 2020 11:35:29 -0800 (PST)
MIME-Version: 1.0
References: <CAD9ie-u_f1fCsTrRtXnk5YHrRHW71EyYiO6xqh9-a=vKTcXp+w@mail.gmail.com> <DM6PR00MB0634A176941D1078F3C655EEA6110@DM6PR00MB0634.namprd00.prod.outlook.com> <CAD9ie-uk33y-5-JiKc6XA_6juGg8Hagp11VW4hwQVepKDFZioA@mail.gmail.com>
In-Reply-To: <CAD9ie-uk33y-5-JiKc6XA_6juGg8Hagp11VW4hwQVepKDFZioA@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Wed, 19 Feb 2020 11:35:03 -0800
Message-ID: <CAD9ie-sSjspU0J3PeHv5hyWktKzXV-xSFg8vPwXAadseg5sXeQ@mail.gmail.com>
To: Anthony Nadalin <tonynad@microsoft.com>
Cc: "oauth@ietf.org" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000172057059ef2e40f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/RPRNaGNgSHukbIA9KlhXlUhw1rs>
Subject: Re: [OAUTH-WG] [EXTERNAL] OAuth 2.1: dropping password grant
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: Wed, 19 Feb 2020 19:35:34 -0000

Tony: are you ok with dropping password grant?

You reference valid use cases. If you think it should continue, would you
provide the use cases?

ᐧ

On Tue, Feb 18, 2020 at 12:57 PM Dick Hardt <dick.hardt@gmail.com> wrote:

> The security topics says MUST. If you want to change that, then that is a
> different discussion. :)
>
> In the OAuth 2.1 document, it would just not be included. Applications can
> continue to be OAuth 2.0 compliant.
>
> BUT ... if there are valid, new use cases. Please describe them! Perhaps
> it should not be dropped.
>
>
> On Tue, Feb 18, 2020 at 12:54 PM Anthony Nadalin <tonynad@microsoft.com>
> wrote:
>
>> I would suggest a SHOULD NOT instead of MUST, there are still sites using
>> this and a grace period should be provided before a MUST is pushed out as
>> there are valid use cases out there still.
>>
>>
>>
>> *From:* OAuth <oauth-bounces@ietf.org> *On Behalf Of * Dick Hardt
>> *Sent:* Tuesday, February 18, 2020 12:37 PM
>> *To:* oauth@ietf.org
>> *Subject:* [EXTERNAL] [OAUTH-WG] OAuth 2.1: dropping password grant
>>
>>
>>
>> Hey List
>>
>>
>>
>> (Once again using the OAuth 2.1 name as a placeholder for the doc that
>> Aaron, Torsten, and I are working on)
>>
>>
>>
>> In the security topics doc
>>
>>
>>
>>
>> https://tools.ietf.org/html/draft-ietf-oauth-security-topics-14#section-2.4
>> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-oauth-security-topics-14%23section-2.4&data=02%7C01%7Ctonynad%40microsoft.com%7C47bb597eef584c95ba4108d7b4b274b2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637176550905333283&sdata=nA1S7TBfZg6cSwY2hI8hpRXhIA2joaaJFmNXrATgr2Y%3D&reserved=0>
>>
>>
>>
>> The password grant MUST not be used.
>>
>>
>>
>> Some background for those interested. I added this grant into OAuth 2.0
>> to allow applications that had been provided password to migrate. Even with
>> the caveats in OAuth 2.0, implementors decide they want to prompt the user
>> to enter their credentials, the anti-pattern OAuth was created to
>> eliminate.
>>
>>
>>
>>
>>
>> Does anyone have concerns with dropping the password grant from the OAuth
>> 2.1 document so that developers don't use it?
>>
>>
>>
>> /Dick
>>
>

v2.23.0 | Report a Bug | By Email