Solved: Unable to set Redirect URI for OOB migration - Page 2

flynnGroup · 10-11-2022 06:34 AM

I am following the steps for the Out-Of-Band (OOB) flow Migration Guide, however, I am unable to set the "redirect uri" when creating credentials for my OAuth client ID, which is for a Desktop Application. Once created I can see that the "redirect_uris" is set to "http://localhost" in the credentials JSON download.

I noticed that if I select Web application then you are given the option to set your "redirect uri" but this is not available for Desktop app.

Is there a way to set the "redirect uri" for a Desktop app? If not are Desktop apps not affected by this change in which case it doesn't matter what is used for the "redirect uri"?

Andre_Fiesco

If not, are Desktop apps not affected by this change in which case it doesn't matter what is used for the "redirect uri"?

The OOB flow is being deprecated for all client types i.e. Web applications, Android, iOS, Universal Windows Platform (UWP), Chrome apps, TVs & limited-input devices, Desktop apps.

Key compliance dates

February 28, 2022 - new OAuth usage blocked for the OOB flow
September 5, 2022 - a user-facing warning message may be displayed to non-compliant OAuth requests
October 3, 2022 - the OOB flow is deprecated for OAuth clients created before February 28, 2022

A user-facing warning message may be displayed for non-compliant requests one month before, i.e. September 5, 2022, the OOB flow is fully deprecated. The message will convey to the users that the app may be blocked soon while displaying the support email that you have registered in the OAuth consent screen in Google API Console.

Is there a way to set the "redirect uri" for a Desktop app?

If you determine that your app is using the OOB flow on a desktop client, you should migrate to using the loopback IP address (localhost or 127.0.0.1) flow.

View solution in original post