Re: [OAUTH-WG] Google's OAuth endpoints now fully support PKCE (RFC7636)

["Nat Sakimura" <[e-mail]>]

Wow, Congratulations, and thanks very much!

 

Best, 

 

--

PLEASE READ :This e-mail is confidential and intended for the

named recipient only. If you are not an intended recipient,

please notify the sender  and delete this e-mail.

 

From: OAuth [mailto:[e-mail]] On Behalf Of William Denniss
Sent: Tuesday, January 19, 2016 2:46 PM
To: [e-mail]
Subject: [OAUTH-WG] Google's OAuth endpoints now fully support PKCE (RFC7636)

 

This month we rolled out full PKCE (RFC7636) support on our OAuth endpoints.

 

We'd previously implemented an earlier draft but were not conformant to the final spec when it was published – now we are. Both "plain" and "S256" transforms are supported. As always, get the latest endpoints from our discovery document: https://accounts.google.com/.well-known/openid-configuration

 

If you give it a spin, let me know how you go! The team monitors the Stack Overflow google-oauth <http://stackoverflow.com/questions/tagged/google-oauth>  tag too, for any implementation questions.

 

I'm keen to know what we should be putting in our discovery doc to declare PKCE support (see the thread "Advertise PKCE support in OAuth 2.0 Discovery"), hope we can agree on that soon.

 

One implementation detail not covered in the spec: we error if you send code_verifier to the token endpoint when exchanging a code that was issued without a code_challenge being present. The assumption being that if you are sending code_verifier on the token exchange, you are using PKCE and should have sent code_challenge on the authorization request, so something is amiss.

 

William