| At line 2 changed one line |
| __Google Drive REST API v3__ based integration: [Google Drive API Link|https://developers.google.com/workspace/drive/api/reference/rest/v3] Authentication is handled through __OAuth 2.0__ ([OAuth Wikipedia Link|https://en.wikipedia.org/wiki/OAuth]), ensuring secure, user-consented access to Google Drive data.\\ |
| __Google Drive REST API v3__ based integration: [Google Drive API Link|https://developers.google.com/workspace/drive/api/reference/rest/v3] Authentication is handled through __OAuth 2.0__ ([OAuth Wikipedia Link|https://en.wikipedia.org/wiki/OAuth]), ensuring secure, user-consented access to Google Drive data.\\ |
| At line 12 added one line |
| __!!!Note:__ Ensure the __Google Drive API__ is enabled at __Enabled APIs & services__. [Google API Library Link|https://console.cloud.google.com/apis/library]\\ |
| At line 13 removed 2 lines |
| __!!!Note:__ Ensure sure the __Google Drive API__ is enabled at __Enabled APIs & services__. [Google API Library Link|https://console.cloud.google.com/apis/library]\\ |
| \\ |
| At line 40 added 3 lines |
| __!!! Note:__ You can configure the __OAuth consent screen__ by clicking the link above the __Authorized JavaScript origins__ section:\\ |
| "The domains you enter in the fields below will be automatically added to your __OAuth consent screen__ as __authorized domains__."\\ |
| Click the link to open the __OAuth consent screen__ settings, complete the configuration, and authorize your __CrushFTP domain.__\\ |
| At line 44 changed 15 lines |
| Now that the API is enabled, and your credentials are setup, and your redirect domains are configured, you can use the credentials in CrushFTP to get your google auth token and get access.\\ |
| __CrushFTP admin page url must match with the redirect url.__ In our example: http://XXXXcrushftp.com\\ |
| In the User Manager, add a new remote VFS item type and set the protocol to be "GDrive".\\ |
| Take your google client_id and secret and combine them together with a tilda as separator:\\ |
| {{{ |
| client_id: 725111111110-7kaimtXXXXXXXXXXXXXXXXXXXXX64m4k.apps.googleusercontent.com |
| secret: fEsXXXXXXXXXXXXXXXXPggg7 |
| }}} |
| results in: |
| {{{ |
| 725111111110-7kaimtXXXXXXXXXXXXXXXXXXXXX64m4k.apps.googleusercontent.com~fEsXXXXXXXXXXXXXXXXPggg7 |
| }}} |
| That whole long string becomes your "username" to GDrive://.\\ |
| Copy and paste it into the user field. Then click "Get Refresh Token" to finish the config.\\ |
| [attachments|get_refresh_token.png]\\ |
| Select the __GDrive__ item type and click the __Get Refresh Token__ button.\\ |
| [GDriveSetup/get_refresh_token.png]\\ |
| At line 60 changed 2 lines |
| Finally!\\ |
| [attachments|test_success.png]\\ |
| __!!! Note__: To obtain the __Refresh Token__, the CrushFTP WebInterface’s host and port must match the __Redirect URL__ specified in the __Google APIs & Services__-> __Credentials__ -> __OAuth 2.0 Client IDs__. In our example, it was: http://127.0.0.1:9090 or https://your.crushftp.domain.com/\\ |
| \\ |
| Enter the __Client ID__ , __Client Secret__. Proceed with the authentication and authorization process.\\ |
| __!!! Note__: Be sure to sign in with the __Google Account__ that has the __necessary permissions__, as configured in the __Google APIs & Services__-> __Credentials__ -> __OAuth 2.0 Client IDs__. This will automatically configure the __User name__ and __Password__.\\ |
| [GDriveSetup/gdrive_oauth_form.png]\\ |
| \\ |
| If the domain is unverified, a warning message may appear. Click __Advanced__ and choose to proceed:\\ |
| \\ |
| [SMTP Google Mail Integration/not_verified_domain.png]\\ |
| \\ |
| Click on the __Allow__ button:\\ |
| \\ |
| [SMTP Google Mail Integration/allow_form.png]\\ |
| \\ |
| [GDriveSetup/test_success.png]\\ |
| \\ |
| __Enable Team Drive__: Enable this option to allow access to __Shared Drives__ (formerly Team Drives) in Google Drive. When selected, file operations will include content stored in Shared Drives, not just the user’s personal My Drive. This is useful when your organization collaborates using __Google Workspace Shared Drives__.\\ |
| \\ |
| __Keep File ID on Overwrite__: Enable this option to __retain the original file’s ID when overwriting a file__ in Google Drive. Instead of deleting and re-uploading the file (which generates a new ID), the existing file is updated in-place. This ensures that any shared links or references to the file remain valid after an overwrite.\\ |
| \\ |
| __Enable MDTM__: Activates support for the __MDTM__ (Modification Time), which allows clients to set the last modified timestamp of a file after the upload action. This can be useful for synchronization tools and backup software that rely on accurate file timestamps.\\ |
| \\ |
| __Corpora variable name__: It defines the logical __buckets__ of content that Google Drive should search within. It’s especially important in complex Drive environments where you may be working across personal drives, shared drives (Team Drives), or content shared with you by others.\\ |
| Values:\\ |
| - user: Search within the current user’s My Drive.\\ |
| - drive: Search within a specific Shared Drive (must be used with driveId).\\ |
| - allDrives: Search across the user’s My Drive and all accessible Shared Drives.\\ |
| - domain: Search all files in the user’s domain (only works with G Suite / Workspace).\\ |
| \\ |
|
|
|
|
