Oracle Database · OAuth Scopes
Oracle Database OAuth Scopes
OAuth 2.0
derived
Oracle Database 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 /ords/{schema}/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.
CloudDatabaseEnterpriseOracleREST APISQL
Scopes: 0
Flows: clientCredentials, authorizationCode
Method: derived
OAuth endpoints
Authorization URL
/ords/{schema}/oauth/auth
/ords/{schema}/oauth/auth
Token URL
/ords/{schema}/oauth/token
/ords/{schema}/oauth/token
Flows
clientCredentialsauthorizationCode
clientCredentialsauthorizationCode
Scopes (0)
Oracle Database 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.
ORDS publishes no fixed OAuth scope catalog — scopes are the user-defined ORDS privilege names protecting each REST module (JWT scope claims must match the privilege name), per https://docs.oracle.com/en/database/oracle/oracle-rest-data-services/25.2/orddg/developing-REST-applications.html.
ORDS publishes no fixed OAuth scope catalog — scopes are the user-defined ORDS privilege names protecting each REST module (JWT scope claims must match the privilege name), per https://docs.oracle.com/en/database/oracle/oracle-rest-data-services/25.2/orddg/developing-REST-applications.html.
📄 Provider scope reference: https://docs.oracle.com/en/database/oracle/oracle-rest-data-services/25.2/orddg/developing-REST-applications.html