Sign in with Google temporarily disabled for this app about drive-cli HOT 26 OPEN

@nurdtechie98 could u get this app verified finally? Not able to use it at all.

from drive-cli.

What worked for me, for some stroke of luck I believe:
Create OAuth client ID credentials at https://console.cloud.google.com/apis/credentials from the +Create Credentials button.
(I believe you have to have a project created for this to be allowed).
Select for "Desktop App" in the dropdown menu. Download the .json file, [re]name it oauth.json and move it to the drive-cli directory. In my case this was a conda env, so ~/anaconda3/envs/env-name/lib/python3.x/site-packages/drive_cli/.
Run "drive [--remote] login" and, at least for me, it solved the google alert and sent me to the confirmation code screen without warnings or otherwise.

Hope this can help 😃

from drive-cli.

@harrego for me it doesn't even show an unsafe link to proceed with

from drive-cli.

Okay, I was able to get a workaround by creating your own oauth credentials on my google account. This gives 100 logins before verification is needed, so that gives you 100 personal devices. Just follow the steps in README.md for the dev branch (although it should work the same for the master branch, just the custom client secret json is required)

For Development
Clone the repo
$ git clone https://github.com/nurdtechie98/drive-cli.git
Get your client_secret.json from Oauth. Make sure to enable Drive Api for the project. Rename the client secret to oauth.json and place it in the drive_cli directory.

Install the package:

    # move into package directory
    $ cd drive-cli
    # install package in edit mode
    $ pip install -e . #note the dot

from drive-cli.

Still experience the problem. @nurdtechie98 is apply process is still going in Google? Any news?

from drive-cli.

Me too :(

from drive-cli.

Looking at enabling unsafe scripts mentioned #86 (comment) I wasn't able to allow for this, as I have 2FA enabled. I also am getting the screen without the 'proceed anyway' option. I am guessing 2FA is causing some issues here.

from drive-cli.

Me too.
Do you guys know anything other that might work for now until drive-cli is verified?

from drive-cli.

Same here... is this app disabled?

from drive-cli.

It seems you need to allow access to insecure applications in your Google account here. I don't feel good doing that

from drive-cli.

Same here :(

from drive-cli.

Same here - even with "allowed access to insecure applications".

from drive-cli.

Don't working :(

from drive-cli.

Sorry for the delay. I have applied for the application to be verified just today. It might take a few weeks for the application to get verified by the google team.
Hope they get back to us soon 🙈

from drive-cli.

Working for me January 26, 2020

from drive-cli.

Me too 27, 2020

from drive-cli.

not working Feb 18, "Sign in with Google temporarily disabled for this app"

from drive-cli.

Is there any workaround?

from drive-cli.

Not working yet.
I suppose the workaround we can try is replacing the oauth mechanism in the scripts to use our IDs for the application. That should make us developers of the application (which we will need to create in our google accounts) that may allow us to use it for ourselves in debug mode.
This is quite frustrating.

from drive-cli.

It appears Google has disabled option 3 manual copy/paste from the OAuth mechanisms (https://developers.google.com/identity/protocols/OAuth2InstalledApp), which I think is what the script uses currently.

Important: The custom URI scheme and loopback IP address options now provide more reliable, secure, and user-friendly ways to obtain user authorization. This option may be discontinued in the future and should only be used if the choices above are not viable.

I suspect they have finally gone ahead with the change and disabled it for all apps. The repo would need to migrate to Option 2 loopback address.

Option 2: Loopback IP address (macOS, Linux, Windows desktop)

To receive the authorization code using this URL, your application must be listening on the local web server. That is possible on many, but not all, platforms. However, if your platform supports it, this is the recommended mechanism for obtaining the authorization code.

When your app receives the authorization response, for best usability it should respond by displaying an HTML page that instructs the user to close the browser and return to your app.
Recommended usage | macOS, Linux, and Windows desktop (but not Universal Windows Platform) apps

from drive-cli.

@mckarthik7 thanks for sharing your workaround. However, I'm failing with setting up the oauth credentials in my google account. It requires me to first create a consent screen and for that i first would need to submit a new app to google. is there some other way to get the oauth credentials?

from drive-cli.

Unfortunately, I wasn't able to find a different way. Thankfully though, it doesn't take too long. It took me about two mins to get it working with this.

from drive-cli.

Same here

from drive-cli.

Still getting the error

from drive-cli.

still, work in process?

from drive-cli.

@souljedi When using your own credentials and presented with the "This app isn't verified..." screen you can just click the "Advanced" button at the bottom and then "Go to [APP NAME]" to auth.

from drive-cli.