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

Sign in with Google (OAuth) disabled pending verification #10900

Closed
cyberduck opened this issue Dec 8, 2019 · 9 comments
Closed

Sign in with Google (OAuth) disabled pending verification #10900

cyberduck opened this issue Dec 8, 2019 · 9 comments
Assignees
Labels
bug fixed googledrive Google Drive Protocol Implementation high priority

Comments

@cyberduck
Copy link
Collaborator

a3380ab created the issue

When I'm adding a new google drive connection, I get routed to the google authentification page. When selecting my account I'm getting

Sign in with Google temporarily disabled for this app - This app has not been verified yet by Google in order to use Google Sign In.

screenshot.png, 800px

Tried with two different google accounts with same result.


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

We are currently awaiting response from Google for our updated registration. As a workaround, register a custom OAuth 2.0 Client ID with Google.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

For Google Storage you can use interoperable access as a workaround.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#10914 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

a80f6b4 commented

Hello, I am overstrained here. Any better isntructions out there how to do the google drive workaround?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

We are in exchange with Google Cloud Platform/API Trust & Safety by emails since Dec 6th.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

6th Dec 2019

Thanks for your reply. A link to the privacy policy is now inclued in the footer of every page at https://cyberduck.io/

Dear Developer,
Thank you for submitting an OAuth App Verification request.

Privacy Policy  

Google API Service:User Data Policy requires the following:

Your Privacy policy must be:

Hosted within the domain of your website
Accessible from the app’s home page
Visible to users
Linked to the OAuth consent screen on the Google API Console
Your privacy policy and in-product privacy notifications must clearly disclose the manner in which your application accesses, uses, stores, or shares Google user data.

Your use of Google user data must be limited to the practices explicitly disclosed in your published privacy policy.

Once your project is updated to reflect these requirements, please reply to this email to confirm your compliance.

If you have additional questions, you can review the OAuth Application Verification FAQ or respond to this email.


-9th Dec 2019*

We cannot show this as long you have blocked our Client ID obviously. The documentation for Cyberduck & Google Drive is available on https://trac.cyberduck.io/wiki/help/en/howto/googledrive. We support accessing Google Docs since 2010 respectively Google Drive since 2016.

Dear Developer,
Thank you for your response.

In order to continue with the verification process, you’ll need to create and provide a link to a YouTube video that shows how you’ll use the data you access using OAuth scopes. Specifically, the demo video should detail, in English:

How to log into your project (ensuring that the URL bar with the client ID is clearly visible)

How to request an OAuth token (OAuth Consent Screen/Permissions Page)

How your project's functionality utilizes the requested scopes:

https://www.googleapis.com/auth/drive

See, edit, create, and delete your Google Drive files

Demonstrate that functionality was successfully achieved.
Please note, we must verify that any changes made via the application, are successfully reflected in the user’s Google Drive.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Dear Developer,
Thank you for submitting a verification request.

Your OAuth App Verification request for project: api-project-996125414232 has been approved for the following scopes:

https://www.googleapis.com/auth/drive
https://www.googleapis.com/auth/devstorage.read_write

@cyberduck
Copy link
Collaborator Author

d5ff845 commented

It's still broken for me.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:18 neik2020]:

It's still broken for me.
We have tested this and the consent screen is no longer being blocked.

@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.
Labels
bug fixed googledrive Google Drive Protocol Implementation high priority
Projects
None yet
Development

No branches or pull requests

2 participants