Re: [OAUTH-WG] OAuth 2.1 - drop implicit flow?

Dick Hardt <dick.hardt@gmail.com> Sat, 07 March 2020 16:06 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 1DF783A08AE for <oauth@ietfa.amsl.com>; Sat, 7 Mar 2020 08:06:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_FONT_LOW_CONTRAST=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 7exvAzRyg18s for <oauth@ietfa.amsl.com>; Sat, 7 Mar 2020 08:06:32 -0800 (PST)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (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 0114B3A08AC for <oauth@ietf.org>; Sat, 7 Mar 2020 08:06:31 -0800 (PST)
Received: by mail-lf1-x12b.google.com with SMTP id z9so4300831lfa.2 for <oauth@ietf.org>; Sat, 07 Mar 2020 08:06: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=p/ydK8veM2ZLOp3W3P2GkjUroxiXRkHMmxMOaFYpAU8=; b=XyLm/Yz0zZ+D2QsQLzuac1DRnhwT7n2fY9nm9LxXqCOFJZO8anChxtPVWWfmO7k0Rj 0QrLCn5N4DIZaXqIpxFKA+6Ixoa5BaUL+JiBycUqmVXoMqJ0E8J7FakgSE5wRYrAPczX GCTRhVkxzILtPsLz5rP8tGWOaazKXyV+kkCSsUMamiAArcegJDUF39JCUeoBGdtuwWVW JAwgUvEx5N4Mokz90AOyJjCVnOdbullVLlum2UqqMox7NzHhKIm05he1w4OqmCTY14ZK pP+61O5lHKufsfUiRRJaPciw11PvSizGG0LJYphalCGvc7ldjyYdtFlni+zopI1+Am4E ZsOQ==
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=p/ydK8veM2ZLOp3W3P2GkjUroxiXRkHMmxMOaFYpAU8=; b=RGNaEK2W+jwU7jVOrNwdRbEqZIldUroEs0Pn8ImrAifwrhu/w3ca8zSJGHezQLK/KI dc99K/zzRV4KICl1cYVPIA0TNZXlYfuJ+fopLmsSaw8z2spjNgfgYiGWjSq58MyNPHZO uU6Do0s9R0nb5UCSNtQsC6EVqob/fXYmf5BWTtIa+MeQIuK8elAnZ9XkGBt9n5QWpfvz eCTjhQxaR9ab672d39vv39QJ5VPwjwM7tknudmkfSB6M8y3Gz24KSWnO+LAm5jmAPCJY w7NCPgwy7558erCfAPj4gFGHjhfb/IuQIO/uDlfZKeJjcG14KDLWGHSJg9e8+bKz40Xi PAaQ==
X-Gm-Message-State: ANhLgQ03khTQyHxFdQ8ZLaIvDDTBW90VaJy1bMeUIqwMjNFwxN95zoH4 2p4pKwp3KfSybiMu1dfFEbOdC0HwEO5prXGPsHc=
X-Google-Smtp-Source: =?utf-8?q?ADFU+vu19Hap/Z8abn8FBnLiAvK+Vw/P+l6QqZlZQUa1?= =?utf-8?q?QxnpdvABI71N8wDGbPW2MizpxHmiRape8xyXiyE11S+2IX8=3D?=
X-Received: by 2002:a19:6513:: with SMTP id z19mr3146161lfb.207.1583597190106; Sat, 07 Mar 2020 08:06:30 -0800 (PST)
MIME-Version: 1.0
References: <CAD9ie-u+egKriB1nvm9CtvFgp4cY1j6sNykGVuTTpsyvR5hA2Q@mail.gmail.com> <CAO7Ng+tUPVfVXQs5MpnO4z5F25WimX-1qeCmLQfrD0Yhbj-ysA@mail.gmail.com> <CAD9ie-v9bvU0s72N0RoHY6y0uwJPK9cCSNCDV2khhD+jveCdHQ@mail.gmail.com> <CA+k3eCRQCa--76c-FYj9=xRJUbpS4UZ9wT6WaFwqNMebKU_iMg@mail.gmail.com>
In-Reply-To: <CA+k3eCRQCa--76c-FYj9=xRJUbpS4UZ9wT6WaFwqNMebKU_iMg@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Sat, 7 Mar 2020 08:06:04 -0800
Message-ID: <CAD9ie-s9HT=9MKPK+GpVngZc+9QMxHS6KL-Sfq-UPQz2VQ3ioA@mail.gmail.com>
To: Brian Campbell <bcampbell@pingidentity.com>
Cc: Dominick Baier <dbaier@leastprivilege.com>, oauth <oauth@ietf.org>, Vittorio Bertocci <Vittorio@auth0.com>
Content-Type: multipart/alternative; boundary="000000000000fbd5e205a045f31a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/bAYwOS6BAqwxOQ0btaBoQ4Weoqc>
Subject: Re: [OAUTH-WG] OAuth 2.1 - drop 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: Sat, 07 Mar 2020 16:06:34 -0000
X-List-Received-Date: Sat, 07 Mar 2020 16:06:34 -0000

How about if we add in a nonnormative reference to OIDC as an explicit
example of an extension:

"For example, OIDC defines an implicit grant with additional security
features."

or similar language
ᐧ

On Sat, Mar 7, 2020 at 5:27 AM Brian Campbell <bcampbell@pingidentity.com>
wrote:

> The name implicit grant is unfortunately somewhat misleading/confusing
> but, for the case at hand, the extension mechanism isn't grant type so much
> as response type and even response mode.
>
> The perspective shared during the office hours call was, paraphrasing as
> best I can, that there are legitimate uses of implicit style flows in
> OpenID Connect (that likely won't be updated) and it would be really nice
> if this new 2.1 or whatever it's going to be document didn't imply that
> they were disallowed or problematic or otherwise create unnecessary FUD or
> confusion for the large population of existing deployments.
>
> On Fri, Feb 28, 2020 at 1:56 PM Dick Hardt <dick.hardt@gmail.com> wrote:
>
>> I'm looking to close out this topic. I heard that Brian and Vittorio
>> shared some points of view in the office hours, and wanted to confirm:
>>
>> + Remove implicit flow from OAuth 2.1 and continue to highlight that
>> grant types are an extension mechanism.
>>
>> For example, if OpenID Connect were to be updated to refer to OAuth 2.1
>> rather than OAuth 2.0, OIDC could define the implicit grant type with all
>> the appropriate considerations.
>>
>>
>> ᐧ
>>
>> On Tue, Feb 18, 2020 at 10:49 PM Dominick Baier <
>> dbaier@leastprivilege.com> wrote:
>>
>>> No - please get rid of it.
>>>
>>> ———
>>> Dominick Baier
>>>
>>> On 18. February 2020 at 21:32:31, Dick Hardt (dick.hardt@gmail.com)
>>> wrote:
>>>
>>> Hey List
>>>
>>> (I'm using the OAuth 2.1 name as a placeholder for the doc that Aaron,
>>> Torsten, and I are working on)
>>>
>>> Given the points Aaron brought up in
>>>
>>> https://mailarchive.ietf.org/arch/msg/oauth/hXEfLXgEqrUQVi7Qy8X_279DCNU
>>>
>>>
>>> Does anyone have concerns with dropping the implicit flow from the OAuth
>>> 2.1 document so that developers don't use it?
>>>
>>> /Dick
>>> _______________________________________________
>>> OAuth mailing list
>>> OAuth@ietf.org
>>> https://www.ietf.org/mailman/listinfo/oauth
>>>
>>>
> *CONFIDENTIALITY NOTICE: This email may contain confidential and
> privileged material for the sole use of the intended recipient(s). Any
> review, use, distribution or disclosure by others is strictly prohibited.
> If you have received this communication in error, please notify the sender
> immediately by e-mail and delete the message and any file attachments from
> your computer. Thank you.*