Migrate to new OAuth flow

[mcamou]

Describe the bug When linking a new Google account, you get a warning stating that the app needs to move to the "more secure OAuth flows". There was an email from Google stating that applications that do not use the more secure OAuth flows will be disallowed on October 3.

More information from that email:

What do I need to do?

• Read the Making Google OAuth interactions safer by using more secure OAuth flows blog post to learn about the deprecation.
• If your apps still need to use the Google OAuth 2.0 authorization endpoint, follow these migration instructions: Follow the Out-of-band (OOB) Migration Guide to migrate your app to an alternative method.
• You may acknowledge the upcoming deadline and suppress a possible user-facing warning message by following instructions in our blog post. All non-compliant authorization requests will be blocked with an invalid_request error when loading Google's OAuth 2.0 authorization endpoint after October 3, 2022.
• If necessary, you may request a one-time deprecation enforcement extension for each listed OAuth client ID until January 31, 2023. For clarity, the enforcement for the OOB flow deprecation will be enforced on February 1, 2023, with no exceptions or extensions. If any of the inactive OAuth clients listed below is no longer needed, remove them from your Google Cloud project by following your client links below.

Desktop (please complete the following information):

• OS: Ubuntu 22.04
• VGrive Version v1.6.1 installed from Flatpak

[eGax]

Yeah, came across this app, looks very promising, but useless without being able to get it authorized to be used with my Google account. Is there any other way to get it authorized? If not, good luck updating. I'll check back at a later time.

[tinkicker]

Maaaaaan! Came here from a lead in a comment about Open Drive for Linux...because it is in the same limbo. Very frustrating.

[resuna]

Just installed the app and Google just plain blocks it now.