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

Dick Hardt <dick.hardt@gmail.com> Sat, 07 March 2020 23:25 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 836E13A1C80 for <oauth@ietfa.amsl.com>; Sat, 7 Mar 2020 15:25:36 -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 nG3Og-kEqi-8 for <oauth@ietfa.amsl.com>; Sat, 7 Mar 2020 15:25:34 -0800 (PST)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (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 0455F3A1C7F for <oauth@ietf.org>; Sat, 7 Mar 2020 15:25:32 -0800 (PST)
Received: by mail-lj1-x22b.google.com with SMTP id d12so6166280lji.4 for <oauth@ietf.org>; Sat, 07 Mar 2020 15:25:32 -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=k+5/XqkiBQkNdZijsilpNOedKCl66MoG9OPeZ2Lke70=; b=FVZDgCQNYnbJD3QuuMpKD9YwFhhzfG9gdNXRyNxlh/ElTscyOWX5XgggiLjDhMkoYM N5ssgxGtr8zHjB5d33FetyiyTJ7SE5XM0TnYAiDZifQizR7XVUKk8wH0i3rm4pWibHxv SJoxzIsOP3e/xjHDuKquv3UkMBQHvjYK/VJv4DefEhXFljYDE/i4N6/YC1G2klWzMutz 5i6rvOINuUAXcRqMafSVhvuyRgn464/TqXCjg4Qjmk32b04f2Wt2PrrYkoDnG2MGhyV/ Dhs1tMrSGH68SotFkT1D3iRrtQrxPuiBrMPyOt44Xt8t/PUUiDeutHAH6T6N89U2sfTy nnLg==
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=k+5/XqkiBQkNdZijsilpNOedKCl66MoG9OPeZ2Lke70=; b=bHqDZ0UoyEJwZxjf5yQWLVbgq1oNj/k7XkeNi8TOB2dKgacvtTungt86vonDKVIalb 8IEYboKUl6JGa6e2pz+kImaeEsaxwLAirzsZygD+qQ74GOn8kD+Ek+pmt3E5prhDkPM1 GqGWTDrt+qnkp+CQYXnqSBPD7sB/KaL+s/bcY+5Y377Pu09odJLci+O5P130jgg6H9v6 qvcauW5h64c8BzKf/Q3bki5Adgi/3mjh5VUDBDKdHCyxZlPyWG2lieKw9eYxS68PMc8e Df1xJmJuQ9k+Pjn4qdeiIKTnlFZzrQmwCq0X+h5pAva4C2HoxAsN71fqFnLCSWYyvrN4 bRpw==
X-Gm-Message-State: ANhLgQ3XNcvxrW7yOKnr4kTYaRpY3yDS2b8S6d0/pfarlj9IgSZj1ac7 TzhBLFVPm3I36sckFYyoaBRE/GIhHtqVr7zX3Vk=
X-Google-Smtp-Source: =?utf-8?q?ADFU+vvA6tS9Ye9qdrZ7FMBdi84B51rrauUDV0WAwdtv?= =?utf-8?q?BqOo98ZWes/VjS0uaYQ64PevsneCSbuDCQRzSkzItEshJ1E=3D?=
X-Received: by 2002:a2e:1653:: with SMTP id 19mr1055984ljw.112.1583623530905; Sat, 07 Mar 2020 15:25:30 -0800 (PST)
MIME-Version: 1.0
References: <CAD9ie-s9HT=9MKPK+GpVngZc+9QMxHS6KL-Sfq-UPQz2VQ3ioA@mail.gmail.com> <3F805BA8-8ABB-4939-96CC-FD2FEC811322@lodderstedt.net> <CAD9ie-sZOG0=pbFW72fZR3XtzsNFRFCyFmF5xeEPFUzHzdmHaQ@mail.gmail.com> <CA+k3eCRJMtAstvrNKPE4qAqU7TCFytrCZC8tHtupWno_J0xKbQ@mail.gmail.com>
In-Reply-To: <CA+k3eCRJMtAstvrNKPE4qAqU7TCFytrCZC8tHtupWno_J0xKbQ@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Sat, 7 Mar 2020 15:25:19 -0800
Message-ID: <CAD9ie-uiLS=f1QrHyQAAaq2YP=gPVFCtOawbKXwh4xG8adw=vQ@mail.gmail.com>
To: Brian Campbell <bcampbell@pingidentity.com>
Cc: Torsten Lodderstedt <torsten@lodderstedt.net>, oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000004828f05a04c1675"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/v5lytImsClc-mWeTI8VXhboz7Jc>
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 23:25:37 -0000

Would you clarify what text works Brian?

On Sat, Mar 7, 2020 at 3:24 PM Brian Campbell <bcampbell@pingidentity.com>
wrote:

> Yeah, that works for me.
>
> On Sat, Mar 7, 2020, 9:37 AM Dick Hardt <dick.hardt@gmail.com> wrote:
>
>> Brian: does that meet your requirements?
>>
>> If not, how about if we refer to OIDC as an example extension without
>> saying it is implicit?
>> ᐧ
>>
>> On Sat, Mar 7, 2020 at 8:29 AM Torsten Lodderstedt <
>> torsten@lodderstedt.net> wrote:
>>
>>> I think keeping the response type as extension point and not mentioning
>>> implicit at all is sufficient to support Brian’s objective.
>>>
>>> Am 07.03.2020 um 17:06 schrieb Dick Hardt <dick.hardt@gmail.com>om>:
>>>
>>> 
>>> 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.*
>>>
>>> _______________________________________________
>>> 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.*