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

Mike Jones <> Mon, 01 February 2016 21:12 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 090231B36DC for <>; Mon, 1 Feb 2016 13:12:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id xpeBeG2Apo_A for <>; Mon, 1 Feb 2016 13:12:46 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 08E031B36D9 for <>; Mon, 1 Feb 2016 13:12:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Eh5Yttrerzrs599McN0W9n6WzvgU2GQC9I9zA6CSPEY=; b=BikJM4ILbhzOq6wBOvfXGsaraYF55unc6qnt71AeQq4QSEoP9gA+GXdT+ovYC9z93z+Kw1gp48lx8OxmqhaF9YKKQAbUlABp5MLPhbFXSUfLeqWFhxITHYSllgyjiCGEBx4hmAPGLTd0dgbVzjunV2vgYkKZHd5ZVL62Hg7UcZ4=
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.1.396.15; Mon, 1 Feb 2016 21:12:43 +0000
Received: from ([]) by ([]) with mapi id 15.01.0396.020; Mon, 1 Feb 2016 21:12:43 +0000
From: Mike Jones <>
To: William Denniss <>
Thread-Topic: [OAUTH-WG] Advertise PKCE support in OAuth 2.0 Discovery (draft-jones-oauth-discovery-00)
Date: Mon, 01 Feb 2016 21:12:43 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results:; dkim=none (message not signed) header.d=none;; dmarc=none action=none;
x-originating-ip: [2001:4898:80e8::595]
x-ms-office365-filtering-correlation-id: 432b5119-d128-4520-e625-08d32b4c6ce1
x-microsoft-exchange-diagnostics: 1; BY2PR03MB441; 5:6swAj+ggC1zyptVF/X8yyMZopUC1eW2En6NLnSNwx6WNaczDCar2XLnfEUziqJcuqeL1iD2+ScnHIjOqxc/oQqVqcZMs6y33V0VcKHITS0l5wE49Bz3BLYF7Zb+0AJHWEdJH/3AiUxi5rp9w+xy0Uw==; 24:fi1dSbU+hnOAjRnU3ZOdnhU1/8jF5cb5btxtmznBSCpcEx5dwqNsKtAYQzW2SuyVY01qBWJwnV3e7eMK0Hq1YLXwVzmpktT9XsGUKyD+TVE=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY2PR03MB441;
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(61426038)(61427038); SRVR:BY2PR03MB441; BCL:0; PCL:0; RULEID:; SRVR:BY2PR03MB441;
x-forefront-prvs: 0839D067E7
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(164054003)(24454002)(377454003)(76176999)(54356999)(230783001)(16236675004)(74316001)(19300405004)(50986999)(77096005)(2950100001)(2900100001)(76576001)(92566002)(33656002)(11100500001)(1220700001)(5001960100002)(110136002)(5008740100001)(10290500002)(15975445007)(3280700002)(86612001)(87936001)(1096002)(3660700001)(2906002)(586003)(19580395003)(19580405001)(102836003)(93886004)(3470700001)(790700001)(6116002)(19617315012)(4326007)(19609705001)(5880100001)(189998001)(99286002)(5002640100001)(122556002)(5004730100002)(106116001)(19625215002)(5003600100002)(40100003)(5005710100001)(10400500002)(86362001)(8990500004)(10090500001)(3826002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR03MB441;; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BY2PR03MB4427FE01334DEAADD6F42D6F5DE0BY2PR03MB442namprd_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Feb 2016 21:12:43.2218 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR03MB441
Archived-At: <>
Cc: "" <>
Subject: Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.0 Discovery (draft-jones-oauth-discovery-00)
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: Mon, 01 Feb 2016 21:12:50 -0000

Congratulations on your deployment!

From: William Denniss []
Sent: Monday, February 1, 2016 12:25 PM
To: Mike Jones <>
Cc: John Bradley <>; Nat Sakimura <>;
Subject: Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.0 Discovery (draft-jones-oauth-discovery-00)

We are now live with this change:

I'm glad we all reached a consensus on how this param should work, and what it should be called, and thank you Mike for revising the draft! My ask now is that we don't revisit this decision, unless for extremely good reasons, as we don't want to break clients who will start using this.

On Mon, Jan 25, 2016 at 4:08 PM, William Denniss <<>> wrote:
Thanks Mike, looking forward to the update. I reviewed the other thread.

On Mon, Jan 25, 2016 at 2:49 PM, Mike Jones <<>> wrote:
I'll add it to the discovery draft in the next day or so.  Also, please see my questions in the message "[OAUTH-WG] Discovery document updates planned". I was waiting for that feedback before doing the update.

-- Mike
From: William Denniss<>
Sent: ‎1/‎25/‎2016 2:29 PM
To: John Bradley<>
Cc: Nat Sakimura<>;<>; Mike Jones<>
Subject: Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.0 Discovery (draft-jones-oauth-discovery-00)
OK great! It seems that we have consensus on this. So this is what we plan to add to our discovery doc, based on this discussion:

"code_challenge_methods_supported": ["plain","S256"]

What are the next steps? Can we we add it to directly? I see that the IANA registry created by that draft is "Specification Required", but PKCE is already an RFC without this param being registered.

On Mon, Jan 25, 2016 at 2:11 PM, John Bradley <<>> wrote:
Yes sorry.   code_challenge_method is the query parameter so code_challenge_methods_supported

On Jan 25, 2016, at 6:12 PM, William Denniss <<>> wrote:

On Thu, Jan 21, 2016 at 6:17 AM, John Bradley <<>> wrote:
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.

To clarify, did you mean "code_challenge_methods_supported"?  That is, building on the param name "code_challenge_method" from Section 4.3<>?

John B.

On Jan 21, 2016, at 3:12 AM, William Denniss <<>> 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 <<>> wrote:
Ah, OK. That's actually reasonable.

2016年1月21日(木) 9:31 nov matake <<>>:
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 <<>> wrote:

Seems like we agree this should be added. How should it look?

Two ideas:

"code_challenge_methods_supported": ["plain", "S256"]


"pkce_methods_supported": ["plain", "S256"]

On Wed, Jan 6, 2016 at 9:59 AM, Torsten Lodderstedt <<>> wrote:

Am 06.01.2016 um 18:25 schrieb William Denniss:

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.

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 mailing list<>


OAuth mailing list<>

OAuth mailing list<>

OAuth mailing list<>

OAuth mailing list<>