[Cyberduck-trac] [Cyberduck] #10900: Sign in with Google (OAuth) disabled pending verification

Cyberduck trac at cyberduck.io
Thu Dec 26 23:33:28 UTC 2019

#10900: Sign in with Google (OAuth) disabled pending verification
 Reporter:  timbo        |         Owner:  dkocher
     Type:  defect       |        Status:  assigned
 Priority:  high         |     Milestone:
Component:  googledrive  |       Version:  7.2.1
 Severity:  blocker      |    Resolution:
 Keywords:               |  Architecture:  Intel
 Platform:  macOS 10.14  |

Comment (by dkocher):

 ''6th December 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:


 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.


Ticket URL: <https://trac.cyberduck.io/ticket/10900#comment:16>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows

More information about the Cyberduck-trac mailing list