This is version 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

Google Drive REST API v3 based integration: Google Drive API Link Authentication is handled through OAuth 2.0 (OAuth Wikipedia Link), ensuring secure, user-consented access to Google Drive data.

!!! Proxy Configuration: If your server accesses the internet through a proxy, make sure to whitelist the following domains for Google Authentication and Drive access:
- oauth2.googleapis.com
- www.googleapis.com

---

1. Google OAuth 2.0 Configuration
#

Start by navigating to Google APIs & Services: Google APIs & Services Link

!!!Note: Ensure sure the Google Drive API is enabled at Enabled APIs & services. Google API Library Link




Go to the Credentials menu, click on Create Credentials, and select OAuth client ID:


Select the application type: Web application. Provide a unique name. Then, configure the Authorized redirect URI—this is where Google will redirect you after authorization. The Redirect URL must end with ?command=register_gdrive_api.

    http://127.0.0.1:9090/?command=register_gdrive_api

or

    
    https://your.crushftp.domain.com/?command=register_gdrive_api
    

Finally, click the Create button.



After the credentials are created, copy the Client ID and Client Secret.

---

2. Gdrive Remote Item Settings:
#

Select the GDrive item type and click the Get Refresh Token button.


!!! 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.