Warning: Google Drive access now only possible via own client id

[Wilhelm M.]

I'm using the old version 2.4 of the plugin - and it also works! Just tried to copy some files. No problem so far.

[Horst.Epp]

I have version 2.6 final

[petermad]

2ghisler(Author)

Also if you have stored your credentials with a master password, you are still logged in from a previous session. The plugin can renew the login token with a refresh token (stored via master password) when it expires.

I tried deleting the key [|FSPlugin|cloudplugin] Google Drive in my wcx_ftp.ini file to provoke the Oauthbrowser login - and I can still login with the 2.60 plugin (BTW the 2.60 plugin shows fileinfo version 2.5.0.0 )

[ghisler(Author)]

Did you get a warning that the app isn't verified? In the Google control panel, it warns me now that the app needs to be verified.

[petermad]

Did you get a warning that the app isn't verified?

No I didn't notice such a thing. I'll try again tomorrow. What do you mean by the Google control panel?

[ghisler(Author)]

I mean this with the control panel: https://console.developers.google.com/
Before Google came up with their bullshit requirements, it was sufficient to configure the app there and get a client id for all users. Now users have to do this themselves.

[petermad]

I mean this with the control panel: https://console.developers.google.com/

I don't have any entries on that control panel - actually just signed in to it today. On that page I see in the top:

Start your Free Trial with $300 in credit. Don’t worry—you won’t be charged if you run out of credits

Is it a demand that I start that trial to get my own client ID and client secret?

[petermad]

I tried deleting the key [|FSPlugin|cloudplugin] Google Drive in my wcx_ftp.ini file to provoke the Oauthbrowser login

tried that again today. After logging into my Google account I get this screen: https://tcmd.madsenworld.dk/oauth.png and after pressing "Tillad" ("allow") everything it up and going as usual - still using plugin v. 2.60

[ghisler(Author)]

That's the normal confirmation screen, not the one I get for new credentials in test mode. Maybe it takes a few more days after they sent me the final warning, or maybe it remains usable for existing users (although this isn't mentioned anywhere). Anyway, just keep the older plugin version for now until it stops working.

[lebans]

I followed your instructions. Now it works flawless. Thanks. Do I need to the same for my android-phone ?

[ghisler(Author)]

I did not get the warning from Google yet for the Android plugin. I received the warning for the Windows Phone version first, then a few months later for the Windows version, so it's only a question of time when I get the same for the Android plugin.

[djorge]

I also folowed the instructions and i can access google drive but before it shows the "google sign in screen", the brower shows a message saying:
"Google hasn’t verified this app
You’ve been given access to an app that’s currently being tested. You should only continue if you know the developer that invited you."

Is this expected or i missed a setting?

[ghisler(Author)]

Yes, this is expected. Verification would cost me up to $75000 per app and year, which is unfortunately unsustainable. Also plugins can't even be verified, I would have to build it into Total Commander itself and re-build Total Commander from the ground up to follow their very specific development rules. This would take several years.

[JOUBE]

I can still access GoogleDrive (various accounts) with the old version of the plugin without any problems. I hope I'm not harming anyone by doing this?

[petermad]

I can still access GoogleDrive

So can I and also after deleting the key [|FSPlugin|cloudplugin] Google Drive in my wcx_ftp.ini and logging in via Oauthbrowser again.

Maybe the problem will only affect new users of the plugin and Google allows previous registered users of the plugin to continue logging in?