Oracle Database 19c · OAuth Scopes
Oracle Database 19c OAuth Scopes
OAuth 2.0
derived
Oracle Database 19c 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://{host}:{port}/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.
DatabaseEnterpriseJsonMachine-LearningNosqlOracleRestSql
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://{host}:{port}/ords/{schema}/oauth/token
https://{host}:{port}/ords/{schema}/oauth/token
Flows
clientCredentials
clientCredentials
Scopes (0)
Oracle Database 19c 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 OAuth 2.0 does not use named scopes; access for OAuth clients is controlled through ORDS privileges (p_privilege_names) and roles granted to the client, per the OAUTH PL/SQL Package Reference (https://docs.oracle.com/en/database/oracle/oracle-rest-data-services/19.4/aelig/OAUTH-reference.html).
ORDS OAuth 2.0 does not use named scopes; access for OAuth clients is controlled through ORDS privileges (p_privilege_names) and roles granted to the client, per the OAUTH PL/SQL Package Reference (https://docs.oracle.com/en/database/oracle/oracle-rest-data-services/19.4/aelig/OAUTH-reference.html).
📄 Provider scope reference: https://docs.oracle.com/en/database/oracle/oracle-rest-data-services/19.4/aelig/OAUTH-reference.html