toohool
toohool

Reputation: 1147

Google OAuth migration: OAuth2 client type does not match OAuth1 consumer type

I have some existing OAuth 1.0 tokens from Google users, and am attempting to exchange them for OAuth 2.0 tokens, as described here.

The request to the /o/oauth2/token endpoint returns the following error response:

{"error": "unauthorized_client",  "error_description" :"OAuth2 client type does not match OAuth1 consumer type."}

My OAuth2 key is registered as a web application, so Google must consider my OAuth1 key as a native application. The Google doc page states that an OAuth1 key is considered a native application if either of the following is true:

I don't have a Chrome extension, and, as far as I know, have never set the native application name (though I can't find any settings page to check this).

Is there some other reason an OAuth1 key would be treated as a native application?

Upvotes: 0

Views: 196

Answers (1)

Miguel Andres
Miguel Andres

Reputation: 1440

We have made a modification to our migration implementation that should have gotten this kind of failures fixed.

We have also updated the migration documentation accordingly.

Upvotes: 1

Related Questions