Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google Drive impossible with Custom OAuth 2.0 Client ID #10915

Closed
cyberduck opened this issue Dec 25, 2019 · 0 comments
Closed

Google Drive impossible with Custom OAuth 2.0 Client ID #10915

cyberduck opened this issue Dec 25, 2019 · 0 comments

Comments

@cyberduck
Copy link
Collaborator

a803e03 created the issue

Hi,

i follow this guide (https://trac.cyberduck.io/wiki/help/en/howto/googleclientid) but doesn't works, because when you select:
../auth/devstorage.read_write
../auth/drive

say: Because you've added a sensitive scope, your consent screen requires verification by Google before it's published. Learn more

'''Verification Status
Needs verification
Because you're using one or more sensitive scopes, your app registration requires verification by Google. Please edit your app to submit for verification.
'''

So, how can is possible for now ?
i miss something or also this workaround doesn't works anymore and for now, cyberduck can't works with google drive?

Thanks for the support

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant