Giant Swarm · OAuth Scopes
Giant Swarm OAuth Scopes
OAuth 2.0
none
Giant Swarm uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
CompanyKubernetesPlatform EngineeringCloud-NativeObservabilityDeveloper PlatformMulti-Cloud
Scopes: 0
Flows:
Method: none
Scopes (0)
Giant Swarm implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.
No OAuth scopes documentation found in Giant Swarm documentation. Authentication uses OAuth2 via Dex and JWT tokens from service accounts, but specific scopes/permissions are not documented.
No OAuth scopes documentation found in Giant Swarm documentation. Authentication uses OAuth2 via Dex and JWT tokens from service accounts, but specific scopes/permissions are not documented.
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.