CODEWITHSUNDEEP
google-oauth
oroman
oroman

Reputation: 61

Creating Production OAuth Client for a Desktop App with redirect URI

I'm in the process of verifying my application, but Google is requesting that I create a PRODUCTION OAuth client with One redirect URI and/or authrozied JavaScript origins URL.

I've poked around everywhere I can think of but I cannot find where I would:

  1. Create a Production OAuth Client - When I create an OAuth Client for my Desktop App, there aren't any options besides Application name
  2. Set a redirect URI and/or authorized JavaScript origins URL - This seems to be applicable to Web Applications, but not Desktop Apps.

I've gone back and forth with support, but I can't get a clear answer. Anyone have any experience with this?

Upvotes: 6

Views: 1845

Answers (1)

Linda Lawton - DaImTo
Linda Lawton - DaImTo

Reputation: 117116

Production Oauth clients are clients that do not have localhost set in the redirect uri or the JavaScript origin. That's probably what they are detecting.

If you have any other clients in this project the first thing i would do is go and check that they don't have localhost set as their redirect Uris or JavaScript origins.

If all you have in this project is desktop applications then continue reading.

OOB flow deprecation.

When creating a desktop app you can only change one thing that being the name

enter image description here (Note: This client was deleted after image taken you cant use it 😉)

In the background google has added a redirect uri of urn:ietf:wg:oauth:2.0:oob and added it to the client. This basically says to the system return the authorization token back to the same place it came from.

Back to your issue:

You are probably being hit by the new Making Google OAuth interactions safer by using more secure OAuth flows changes.

These changes mainly effect desktop applications. Ordinally the desktop client type used. The OAuth out-of-band (oob) flow. This flow used a refresh token called.

redirect_uri=urn:ietf:wg:oauth:2.0:oob or urn:ietf:wg:oauth:2.0:oob:auto or oob

The new changes removes that flow dates-oob and its kicking in this week.

It sounds like by the error message you are getting that they are totally removing that type of client. I was assured by Google that we would be given a grace period in which developers would have time to update their apps to use the new system. I question wither or not this also counted for verification.

If this is the case then I have no solution but I can contact google for you to see if there is any issues with verification and desktop apps now.

Upvotes: 2

Related Questions