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 05:38 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 ECDEB1B2F9B for <oauth@ietfa.amsl.com>; Wed, 20 Jan 2016 21:38:12 -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 0yJ9jXMN1f1h for <oauth@ietfa.amsl.com>; Wed, 20 Jan 2016 21:38:11 -0800 (PST)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (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 C3E191B2F9A for <oauth@ietf.org>; Wed, 20 Jan 2016 21:38:10 -0800 (PST)
Received: by mail-qk0-x235.google.com with SMTP id o6so12195944qkc.2 for <oauth@ietf.org>; Wed, 20 Jan 2016 21:38:10 -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=l3fMnafhnmTvbmAL8etNyfZ9RMDq5TKG8Y2ZHgZbezg=; b=R76Xs6sxBmIH5inHVvOsV8S/XHN7FWJkd56cnLlUxgHSmlWBNLu6FYaj0SG6yQD8lR TjIsQgJLQHCxNsxoVPPz7BoRYLbLurr2V76JkkhCWxBpBYA0U5imhKW+ajB4tu1ow7P9 DLD/dYhwRkV6/AsB0DBqi7LygDgCxhiVJRuAuqzATlBoBw4vuKKB3kGKNjg6jHRLdylB IyvvoKz6ZyaIiN+1X+3cd/BxuMAeJNaQMF8Eee9uyCXPgy42teukJ9AUX2uVk9/cZ2hQ Z69lx5AYGsAEaWWM432WioCXJY5I+hIartSM0G7HzDMVWbDa3itVp4SALeYFgmr3w2rC pXCQ==
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=l3fMnafhnmTvbmAL8etNyfZ9RMDq5TKG8Y2ZHgZbezg=; b=GQSRN8AJIdWv3AmQ4UE9K0Tz6sXzI+U8ZpuCETd5dSeDvY+bl+SycIkrcpB69qQma1 US7DSOn+cVo8C4rdj4N7wds1sV7tR7S+W3IdAuFTjqHVSSiN9D4+uzwUXoR616ze1+Ug PuYWV2HuWJ+oEucRi2Blptin6pxj+WCXqYlWDbZXDCOv2w+7iYqgA/nmCd/x9y3BhwKJ Dosu1Fg3gbRbPu127WdNHvsSXj7+zoFxBGWdPM+LP5GtFrOf1ewAbMNNK/G+nLyx+2nB e9DEiOIsNxqNwNo62P+re//ttfbAyJM0ERaBPK71jVHcm7kflupeMh1ACDFSlK7ZFwRD BChw==
X-Gm-Message-State: ALoCoQl71hFqYEXIE2V1X0Msr91NMuzUIh4+rdOXY92py6IYPZZRsHxu2Gl6WClyAiK6NWYBhCZtkgQcnT2Uk2yrhmV4iTfqGA==
X-Received: by 10.55.20.211 with SMTP id 80mr49511784qku.67.1453354689927; Wed, 20 Jan 2016 21:38:09 -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>
In-Reply-To: <F9C0DF10-C067-4EEB-85C8-E1208798EA54@gmail.com>
From: Nat Sakimura <sakimura@gmail.com>
Date: Thu, 21 Jan 2016 05:37:59 +0000
Message-ID: <CABzCy2A+Z86UCJXeK1mLPfyq9p1QQS=_dekbEz6ibP8Z8Pz87Q@mail.gmail.com>
To: nov matake <matake@gmail.com>, William Denniss <wdenniss@google.com>
Content-Type: multipart/alternative; boundary="001a11449546069dc00529d18245"
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/UCVUI_pGFrb2GPDevIqDkqdnbZk>
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 05:38:13 -0000
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-WG] Advertise PKCE support in OAuth 2.0 Di… Vladimir Dzhuvinov
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… John Bradley
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… William Denniss
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… Torsten Lodderstedt
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… William Denniss
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… Nat Sakimura
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… nov matake
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… Nat Sakimura
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… William Denniss
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… John Bradley
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… Nat Sakimura
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… Phil Hunt
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… William Denniss
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… John Bradley
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… William Denniss
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… Mike Jones
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… William Denniss
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… William Denniss
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… Mike Jones
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… Dominick Baier
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… Dominick Baier