Presto Foundation · OAuth Scopes
Presto Foundation OAuth Scopes
OAuth 2.0
derived
Presto Foundation 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.
Tokens are issued from https://example.com/oauth/token.
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.
AnalyticsBig DataDistributed SQLLinux FoundationOpen SourceQuery EngineSQL
Scopes: 0
Flows: authorizationCode
Method: derived
OAuth endpoints
Authorization URL
https://example.com/oauth/authorize
https://example.com/oauth/authorize
Token URL
https://example.com/oauth/token
https://example.com/oauth/token
Flows
authorizationCode
authorizationCode
Scopes (0)
Presto Foundation 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.
Presto does not publish its own OAuth scopes; OAuth 2.0 is an optional coordinator authenticator using OIDC where scopes (e.g. openid, email, profile) are configured per deployment via http-server.authentication.oauth2.scopes for the external identity provider (https://prestodb.io/docs/current/security/oauth2.html).
Presto does not publish its own OAuth scopes; OAuth 2.0 is an optional coordinator authenticator using OIDC where scopes (e.g. openid, email, profile) are configured per deployment via http-server.authentication.oauth2.scopes for the external identity provider (https://prestodb.io/docs/current/security/oauth2.html).
📄 Provider scope reference: https://prestodb.io/docs/current/security/oauth2.html