Device Flow: verification_uri vs verification_url for Google.

[nikolay-turpitko]

I'm checking newly implemented Device Flow and I've found a minor issue.
Here:

type DeviceAuthResponse struct {
   VerificationURI string `json:"verification_uri"` 
}

Verefication URI is decoded from JSON field, named according RFC.

But here, Google uses verification_url name. Which is, obviously, contradicts spec, but it would be nice to be able to somehow obtain it anyway.

Would it be possible to add raw data field to DeviceAuthResponse, or map with all received fields, or map with additional (not parsed) fields from the response JSON?

[nikolay-turpitko]

@hickford Could you please check?

[hickford]

Google uses verification_url which contradicts spec RFC 8628 verification_uri

Have you reported this at developers.google.com?

[hickford]

Here's a two-line fix that avoids changing the API #667

[nikolay-turpitko]

Have you reported this at developers.google.com?

No, I haven't, TBH. From my previous experience it never helps with big corporations.

Here's a two-line fix that avoids changing the API #667

This works perfectly!

[bcmills]

This appears to be https://issuetracker.google.com/issues/151238144.