GCP GCS

Google's APIs follow a different authentication scheme, that cannot work autonomously like AWS's signature mechanism.

In GCS, line in any other Google's services, we require the existence of an authentication endpoint to generate a valid token.

This token is then later used in every request to the GCS API to verify the identity and permissions of the requester.

This is why all Flashback nodes implement a custom /token OAuth2 endpoint.

The only requirement to use Flashback GCS client SDKs on Flashback nodes is indicating the endpoint URL you want to use, and provide the custom token URI or use a derived custom OAuth2 client class, and then pass one of the valid repo generated API keys.

We tested the platform with the following SDKs:

• Node.js

npm install @google-cloud/storage google-auth-library

# if you want to use our custom OAuth2 client:
npm install @flashbacktech/flashbackclient@latest

• Python

pip install google-cloud-storage>=2.14.0

• Rust

# Cargo.tomp Google GCS
google-cloud-storage = "0.24.0"
google-cloud-auth = { version = "0.17.2", features = ["external-account"] }
google-cloud-token = "0.1.2"