Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.0 Discovery (draft-jones-oauth-discovery-00)

Nat Sakimura <sakimura@gmail.com> Thu, 21 January 2016 14:26 UTC

Return-Path: <sakimura@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52B2C1A87D9 for <oauth@ietfa.amsl.com>; Thu, 21 Jan 2016 06:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 76xp3jMSQK1S for <oauth@ietfa.amsl.com>; Thu, 21 Jan 2016 06:26:19 -0800 (PST)
Received: from mail-qg0-x229.google.com (mail-qg0-x229.google.com [IPv6:2607:f8b0:400d:c04::229]) (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 073CB1A87A5 for <oauth@ietf.org>; Thu, 21 Jan 2016 06:26:19 -0800 (PST)
Received: by mail-qg0-x229.google.com with SMTP id 6so32496577qgy.1 for <oauth@ietf.org>; Thu, 21 Jan 2016 06:26:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=J4LzLR1YWVkdSx69Ro3ZOsCo4KNVvenXdT6prMFPjU4=; b=ipDefOiDqtqrXls5+E7M5eMu84pDZjZHTg+UguZhFEpGS9AovSvCVEG1L6UmpqPpGd LYBQr1j9MtFA2hQgZN/Io2y1JnvcK6OZler66fjA9Ns27RQKR12lbVyXBRDND3d6cinr 9dNWHD+5m9RbG8mPQutLog1kW+vAQE48xWFJMC9TXdsSvjOvy/kabvCrMJ7DqhCGqIbW eM4HpKFsXevaIRD5/sm6/CfaRIMZeLYGoOaKMWL6Gd93NDvmDJpcfe5baG5Ib71hWhAR DbeHjUW87Jp9V+5Mqo4ZQ/PHJjL/ppHl8rHUhj+TmpQknyWUtPQlTMxBcekS281+GLW8 wBIA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-type; bh=J4LzLR1YWVkdSx69Ro3ZOsCo4KNVvenXdT6prMFPjU4=; b=cQlHHfHDaDCweGNINjuJz0YQFGYAPG139uYzlwzK5jXq6EnEIjwzcP6oyuVVG5JGvk rLsao9KVoajGwVk7/IXh5366CjJwgtg577x85tRPtO+k7vvLYYX1sXU+o/P3P2BeaHPf LBte1rYZUUJVcsOjGH8S1F+f52A4tR7YU11VI4AtZMNN6RmovAY+z9b+n4EaPernH6xC qsStpjHSqPWbfmfqmXXYNkzLRMI/yCmNwJ4GI1u2oRsC/utD3UOd4TjG6Ey88I3hm+/b Lh6qjpqppK/0wnuBjwuymky/GV7VNuaDN3JubqZ+V313zcE4B0yBg4Pu0NBYElh9guzC RDPw==
X-Gm-Message-State: ALoCoQkulnWSiLROofN5uEH+qxHlEEQGgmJeweNZ+Ar5zaWn0vVH1SUj07MEql8WctoCXY/eE7I2Nd1W2GVo/2rFIA9eW9VwqA==
X-Received: by 10.140.101.201 with SMTP id u67mr52621034qge.33.1453386377943; Thu, 21 Jan 2016 06:26:17 -0800 (PST)
MIME-Version: 1.0
References: <568D24DD.3050501@connect2id.com> <EA392E73-1C01-42DC-B21D-09F570239D5E@ve7jtb.com> <CAAP42hAA6SOvfxjfuQdjoPfSh3HmK=a7PCQ_sPXTmDg+AQ6sug@mail.gmail.com> <568D5610.6000506@lodderstedt.net> <CAAP42hA8SyOOkJ-D299VgvQUdQv6NXqxSt9R0TK7Zk7JaU56eQ@mail.gmail.com> <F9C0DF10-C067-4EEB-85C8-E1208798EA54@gmail.com> <CABzCy2A+Z86UCJXeK1mLPfyq9p1QQS=_dekbEz6ibP8Z8Pz87Q@mail.gmail.com> <CAAP42hCKRpEnS7zVL7C_jpaFXwXUjzkNUzxtDa9MUKAQw7gsAA@mail.gmail.com> <10631235-AF1B-4122-AEAE-D56BBF38F87E@ve7jtb.com>
In-Reply-To: <10631235-AF1B-4122-AEAE-D56BBF38F87E@ve7jtb.com>
From: Nat Sakimura <sakimura@gmail.com>
Date: Thu, 21 Jan 2016 14:26:08 +0000
Message-ID: <CABzCy2B5AAMLPj+R2-qUC0X06Ny+j9ctORnt0w36YYzuZTNzrA@mail.gmail.com>
To: John Bradley <ve7jtb@ve7jtb.com>, William Denniss <wdenniss@google.com>
Content-Type: multipart/alternative; boundary=001a11c16e6ac7613a0529d8e271
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/wQzAzDyMzP2IVsq9nBHN-vuWETg>
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.0 Discovery (draft-jones-oauth-discovery-00)
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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, 21 Jan 2016 14:26:21 -0000

+1. Even as the main editor of the spec., I tend to forget the history ;-)

2016年1月21日(木) 23:17 John Bradley <ve7jtb@ve7jtb.com>;:

> The code_challenge and code_challenge_method parameter names predate
> calling the spec PKCE.
>
> Given that some of us deployed early versions of PKCE in products and
> opensource to mitigate the problem before the spec was completed we decided
> not to rename the parameter names from code_verifier_method to
> pkce_verifier_method.
>
> For consistency we should stick with code_verifier_methods_supported in
> discovery.
>
> John B.
>
> On Jan 21, 2016, at 3:12 AM, William Denniss <wdenniss@google.com>; wrote:
>
> "code_challenge_methods_supported" definitely works for me.
>
> Any objections to moving forward with that? I would like to update our
> discovery doc shortly.
>
> On Thu, Jan 21, 2016 at 1:37 PM, Nat Sakimura <sakimura@gmail.com>; wrote:
>
>> Ah, OK. That's actually reasonable.
>>
>> 2016年1月21日(木) 9:31 nov matake <matake@gmail.com>;:
>>
>>> I prefer “code_challenge_methods_supported”, since the registered
>>> parameter name is “code_challenge_method”, not “pkce_method".
>>>
>>> On Jan 19, 2016, at 11:58, William Denniss <wdenniss@google.com>; wrote:
>>>
>>> Seems like we agree this should be added. How should it look?
>>>
>>> Two ideas:
>>>
>>> "code_challenge_methods_supported": ["plain", "S256"]
>>>
>>> or
>>>
>>> "pkce_methods_supported": ["plain", "S256"]
>>>
>>>
>>>
>>> On Wed, Jan 6, 2016 at 9:59 AM, Torsten Lodderstedt <
>>> torsten@lodderstedt.net>; wrote:
>>>
>>>> +1
>>>>
>>>>
>>>> Am 06.01.2016 um 18:25 schrieb William Denniss:
>>>>
>>>> +1
>>>>
>>>> On Wed, Jan 6, 2016 at 6:40 AM, John Bradley <ve7jtb@ve7jtb.com>; wrote:
>>>>
>>>>> Good point.  Now that PKCE is a RFC we should add it to discovery.
>>>>>
>>>>> John B.
>>>>> > On Jan 6, 2016, at 9:29 AM, Vladimir Dzhuvinov <
>>>>> vladimir@connect2id.com>; wrote:
>>>>> >
>>>>> > I just noticed PKCE support is missing from the discovery metadata.
>>>>> >
>>>>> > Is it a good idea to add it?
>>>>> >
>>>>> > Cheers,
>>>>> >
>>>>> > Vladimir
>>>>> >
>>>>> > --
>>>>> > Vladimir Dzhuvinov
>>>>> >
>>>>> >
>>>>> > _______________________________________________
>>>>> > OAuth mailing list
>>>>> > OAuth@ietf.org
>>>>> > https://www.ietf.org/mailman/listinfo/oauth
>>>>>
>>>>> _______________________________________________
>>>>> OAuth mailing list
>>>>> OAuth@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/oauth
>>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> OAuth mailing listOAuth@ietf.orghttps://www.ietf.org/mailman/listinfo/oauth
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> OAuth mailing list
>>> OAuth@ietf.org
>>> https://www.ietf.org/mailman/listinfo/oauth
>>>
>>>
>>> _______________________________________________
>>> OAuth mailing list
>>> OAuth@ietf.org
>>> https://www.ietf.org/mailman/listinfo/oauth
>>>
>>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
>
>