OIDC federation
Code in a deployed Function calls the Gigadrive Network API as itself, with no API key for you to create, store, or rotate.
Every Function you deploy to Gigadrive Network gets its own OAuth 2.0 credential. Code running inside it calls the API as itself, so there is no key for you to create in a dashboard, paste into an environment variable, and remember to rotate.
The platform mints the credential while the deployment is being provisioned, hands it to the Function as environment variables, and deletes it when the deployment's Functions go away. It carries sixteen scopes: enough to read and write storage objects, send and consume queue messages, start and drive microVMs, mint a sticky session URL, and use the runtime cache. Nothing that changes your infrastructure.
Inside a Function, new GigadriveClient() takes no arguments and works.
How it works
Where the credential comes from, how it reaches your code, and when it stops working.
Injected variables
Every GIGADRIVE_ variable the platform sets inside a Function, and when each is present.
Function scopes
The sixteen scopes a Function's token carries, and what stays out of reach.
Using the SDK
The zero-config client in production, and credentials for local development.
OIDC provider
Discovery, the token endpoint, and verifying a token yourself.