Gigadrive IDP
The OpenID Connect provider behind Gigadrive sign-in, who can use it, and how to ask for a client.
Access is granted per request
The Gigadrive IDP is not open to public sign-up, and there is no dynamic client registration endpoint. A client is
created for you after Gigadrive reviews the request. Ask at cs@gigadrive.de before you build against it.
idp.gigadrive.de is a standards-compliant OpenID Connect provider for people. It is what signs users into the Gigadrive console, the CLI, and the account pages, and it is what an approved third-party application uses to let people sign in with their Gigadrive account.
The two issuers, which are not interchangeable
idp.gigadrive.de | api.gigadrive.network | |
|---|---|---|
| Authenticates | People | Machines |
| Credential | An OAuth client plus a user session | An API key |
| Grants | Authorization code with PKCE, refresh token, device code | Client credentials only |
| Endpoints | Authorize, token, userinfo, revoke, device authorization, discovery, JWKS | Token, discovery, JWKS |
| Use it when | A human needs to sign in | A job needs to call the API |
Both issue RS256 bearer tokens and the Gigadrive API accepts either on the same Authorization header. For deployment automation, use an API key and the api.gigadrive.network issuer instead of the account IDP.
How to ask for a client
Write to cs@gigadrive.de with what you are building, the redirect URIs it will use, whether it can keep a secret, and the scopes it needs. Requesting access lists exactly what to include and what comes back.
There is no self-service path. Every client is a way for a third party to receive claims about Gigadrive users, and some scopes reach real resources rather than a name and an email address, so each request is reviewed.