1. Google Cloud Storage REST API
#
Cloud Storage JSON REST API based integration: Cloud Storage JSON REST API Link

!!! 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
- storage.googleapis.com
Start by navigating to Google APIs & Services: Google APIs & Services Link

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



1.1 Configure access through a Web Application OAuth client
#
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.

!!! 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.
GStorage Remote Item Settings:
Select the GStorage 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.

If the domain is unverified, a warning message may appear. Click Advanced and choose to proceed:

Click on the Allow button:

Provide the Google Storage Bucket and the path.

1.2. Configure access using a Service Account OAuth client
#
Create Credentials -> Service Account.

Provide a name and continue.

Configure the service account access.

Click on the "Done" button.
Navigate to the newly created Service Account. Go to the KEYS tab. Click on the Add KEY button, and then select Create new key.

Download the JSON file.

VFS configuration:
Username: google_jwt -> Special user name for Service Account Access.
Password: <<the JSON file content>> -> It authenticates based on the provided JSON file.
Provide the bucket and the path.
It is done! Test the connection and save it!

2. Access through S3 REST API
#
Generate Access key and Secret. Got to Google Console Cloud Link


Select the Interoperability tab. If you haven't enabled it already, click on Interoperable Access. Now you should see an empty list and a Create New Key button. Click the button to create an Access/Secret key pair.
Google Cloud S3 VFS configuration:
1.
Domain: <<Cloud Storage -> Settings -> INTEROPERABILITY -> Domain of Storage URI default is storage.googleapis.com>>
Change the S3 default domain (s3.amazonaws.com) to the domain of Google Cloud Storage domain.
User name:<<Access Key>>
Password:<<Secret>>
Bucket:<<Google Cloud Storage Bucket Name>>
SHA256 enabled on signing (Signing Version 4):<<Enabled>>
!Warning Signing version 4 must be enabled, as Google Cloud Storage does not support older signing versions.

2. Select GStorage Item type.
Enable S3 API flag.
Domain:<<Cloud Storage -> Settings -> INTEROPERABILITY -> Domain of Storage URI default is storage.googleapis.com>>
Change the S3 default domain (s3.amazonaws.com) to the domain of Google Cloud Storage domain.
User name: <<Access Key>>
Password: <<Secret>>
Bucket: <<Google Cloud Storage Bucket Name>>
SHA256 enabled on signing (Signing Version 4):<<Enabled>>
!Warning Signing version 4 must be enabled, as Google Cloud Storage does not support older signing versions.

More info about s3 VFS configuration: S3 integration
Add new attachment
Only authorized users are allowed to upload new attachments.
List of attachments
Kind | Attachment Name | Size | Version | Date Modified | Author | Change note |
---|---|---|---|---|---|---|
png |
allow_form.png | 100.3 kB | 1 | 05-Dec-2023 05:32 | krivacsz | |
png |
bucket_and_test.png | 250.0 kB | 2 | 05-Dec-2023 05:32 | krivacsz | |
png |
clopud_storage_api_enable.png | 47.1 kB | 1 | 05-Dec-2023 05:32 | krivacsz | |
png |
cloud_storage_sttings.png | 63.4 kB | 1 | 05-Dec-2023 05:32 | krivacsz | |
png |
gstroage_s3_api_vfs_enabled.pn... | 174.9 kB | 1 | 05-Dec-2023 05:32 | krivacsz | |
png |
not_verified_domain.png | 111.6 kB | 1 | 05-Dec-2023 05:32 | krivacsz | |
png |
oauth_form.png | 61.3 kB | 1 | 05-Dec-2023 05:32 | krivacsz | |
png |
s3_vfs_settings.png | 210.0 kB | 1 | 05-Dec-2023 05:32 | krivacsz | |
png |
service_account.png | 113.5 kB | 1 | 05-Dec-2023 05:32 | krivacsz | |
png |
service_account_details.png | 83.7 kB | 1 | 05-Dec-2023 05:32 | krivacsz | |
png |
service_account_new_key.png | 72.9 kB | 1 | 05-Dec-2023 05:32 | krivacsz | |
png |
service_account_private_key.pn... | 41.0 kB | 1 | 05-Dec-2023 05:32 | krivacsz | |
png |
service_acount_vfs_test.png | 130.7 kB | 1 | 05-Dec-2023 05:32 | krivacsz | |
png |
storage_account_access.png | 121.4 kB | 1 | 05-Dec-2023 05:32 | krivacsz |
«
This page (revision-74) was last changed on 15-May-2025 08:54 by krivacsz
G’day (anonymous guest)
Log in
JSPWiki