Return-Path: 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 B40281ACE69 for ; Wed, 20 Jan 2016 16:31:10 -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 7tSXpUrbK-qn for ; Wed, 20 Jan 2016 16:31:09 -0800 (PST) Received: from mail-pf0-x22b.google.com (mail-pf0-x22b.google.com [IPv6:2607:f8b0:400e:c00::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 B50161B2B98 for ; Wed, 20 Jan 2016 16:31:07 -0800 (PST) Received: by mail-pf0-x22b.google.com with SMTP id n128so13113439pfn.3 for ; Wed, 20 Jan 2016 16:31:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=XJbFmfAlrVz4LltpFUmH6f9WMhrXAdBM/gW9J2j1vKI=; b=KIV+fYWxaSSyCc3azCTqEr1g9h1Dd/nbvfDDh7tIVZfiPxFlsXEDY08wnDPZt44l9y i3fqzfCLPO2DeHuUUezEnVBzjkNeDITJeeCEm72h+X5OS3o0tnr7P1B6EUsmCmhtsK5t fQZuypyI+D7hOGS5W3Hn5Lf6pv0Mf2A9wN9bb9t33YcD7BVQMjudQL67dbUJzSSJqJ6w UMsPi8a9bq032IdsNdohEeOX3psetF3wUU+qrP7qR4yroiEOpz3QryVXkDkkysAY4tTm vsgg5Jy5IVjKNLGNhMN9zLY9KFDNNO2trAfqy6gRObR8FvZ2zdzW0Pw2GQwAqH/UNpHH JS0g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=XJbFmfAlrVz4LltpFUmH6f9WMhrXAdBM/gW9J2j1vKI=; b=Hk2eLlBdUb9THxjZgDLQa5QjpVFn9BgUEnJcJEIWte9xNP9d8Ht7+FRx4TK+i8HjFo WkY99TOFbDbulRcThQMjG9aBuywoXoAbdX1whWy20jhPpSy0DOAwKrD8GJJyhZ/l46On OG2bPaf43k1E99BhcsgKr66OodJDzQmeBFFgvwaKe2HH69HVvsiaR+vY94lkIuoV2036 8LSzXnlgJ3zPC3fYwwOX6cN9pJeeuH32uBPUU8HHGDJ4cl2HRlwxyoykL27P3By77YYQ NKG0xb6Wk4nDs9/2Yz4956YLEf2ngd3Qa1Gv37SpEAZGetvsQh3f49gaYnX+XxbOF9hZ BPBA== X-Gm-Message-State: ALoCoQk+ViIiL14VcZ3wsZUt7JOxhBzOCDFoUvUWjeOuJ4fkZY7ruOmea1VxbfSXy5ypvFcJ5e5Pu2HkFYReUbLmdyCDcYANiQ== X-Received: by 10.98.17.142 with SMTP id 14mr56056115pfr.37.1453336267231; Wed, 20 Jan 2016 16:31:07 -0800 (PST) Received: from [192.168.1.16] (122x210x153x65.ap122.ftth.ucom.ne.jp. [122.210.153.65]) by smtp.gmail.com with ESMTPSA id 72sm51268080pfk.28.2016.01.20.16.31.05 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 20 Jan 2016 16:31:06 -0800 (PST) Content-Type: multipart/alternative; boundary="Apple-Mail=_DFF07BB5-45F0-49E7-B03F-6A8FD2C984E1" Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) From: nov matake In-Reply-To: Date: Thu, 21 Jan 2016 09:31:03 +0900 Message-Id: References: <568D24DD.3050501@connect2id.com> <568D5610.6000506@lodderstedt.net> To: William Denniss X-Mailer: Apple Mail (2.3112) Archived-At: Cc: "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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jan 2016 00:31:10 -0000 --Apple-Mail=_DFF07BB5-45F0-49E7-B03F-6A8FD2C984E1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I prefer =E2=80=9Ccode_challenge_methods_supported=E2=80=9D, since the = registered parameter name is =E2=80=9Ccode_challenge_method=E2=80=9D, = not =E2=80=9Cpkce_method". > On Jan 19, 2016, at 11:58, William Denniss = wrote: >=20 > Seems like we agree this should be added. How should it look? >=20 > Two ideas: >=20 > "code_challenge_methods_supported": ["plain", "S256"] >=20 > or >=20 > "pkce_methods_supported": ["plain", "S256"] >=20 >=20 >=20 > On Wed, Jan 6, 2016 at 9:59 AM, Torsten Lodderstedt = > wrote: > +1 >=20 >=20 > Am 06.01.2016 um 18:25 schrieb William Denniss: >> +1 >>=20 >> On Wed, Jan 6, 2016 at 6:40 AM, John Bradley > wrote: >> Good point. Now that PKCE is a RFC we should add it to discovery. >>=20 >> John B. >> > On Jan 6, 2016, at 9:29 AM, Vladimir Dzhuvinov = > 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 = >>=20 >> _______________________________________________ >> OAuth mailing list >> OAuth@ietf.org >> https://www.ietf.org/mailman/listinfo/oauth = >>=20 >>=20 >>=20 >> _______________________________________________ >> OAuth mailing list >> OAuth@ietf.org >> https://www.ietf.org/mailman/listinfo/oauth = >=20 >=20 > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth --Apple-Mail=_DFF07BB5-45F0-49E7-B03F-6A8FD2C984E1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 I prefer =E2=80=9Ccode_challenge_methods_supported=E2=80=9D, = since the registered parameter name is =E2=80=9Ccode_challenge_method=E2=80= =9D, not =E2=80=9Cpkce_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:
=20 =20 =20
+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 list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth


_______________________________________________
OAuth = mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

= --Apple-Mail=_DFF07BB5-45F0-49E7-B03F-6A8FD2C984E1--