Oracle Partitioning · OAuth Scopes
Oracle Partitioning OAuth Scopes
OAuth 2.0
searched
Oracle Partitioning 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 /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.
Agent SkillsComposite-PartitioningData DictionaryDatabaseEnterprise Edition OptionHash-PartitioningInterval-PartitioningList-PartitioningMCPORDSOracleOracle DatabasePartitioningPerformanceRange-PartitioningSQLScalabilityTable PartitioningVLDB
Scopes: 0
Flows: implicit, authorizationCode, clientCredentials
Method: searched
OAuth endpoints
Authorization URL
/oauth/auth
/oauth/auth
Token URL
/oauth/token
/oauth/token
Flows
implicitauthorizationCodeclientCredentials
implicitauthorizationCodeclientCredentials
Scopes (0)
Oracle Partitioning 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.
📄 Provider scope reference: https://docs.oracle.com/en/database/oracle/oracle-rest-data-services/26.2/ordig/configuring-model-context-protocol-mcp.html
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.