Oracle Siebel · OAuth Scopes

Oracle Siebel OAuth Scopes

OAuth 2.0 searched

Oracle Siebel 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.

CRMCustomer ManagementEnterprise SoftwareMarketing AutomationOracleSales AutomationService Automation
Scopes: 0 Flows: Method: searched

Scopes (0)

Oracle Siebel 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/cd/G30562_01/books/Secur/c-Using-OAuth-with-REST-Inbound-Web-Services.html

Source

OAuth Scopes

Raw ↑ 
generated: '2026-08-13'
method: searched
source: >-
  https://docs.oracle.com/cd/G30562_01/books/Secur/c-Using-OAuth-with-REST-Inbound-Web-Services.html
  and https://docs.oracle.com/cd/F26413_26/books/Secur/index.html, read against
  the oauth2 securitySchemes declared in openapi/*.yml
docs: https://docs.oracle.com/cd/G30562_01/books/Secur/c-Using-OAuth-with-REST-Inbound-Web-Services.html
provider: Oracle Siebel
providerId: oracle-siebel
scope_count: 0
scopes: []
summary: >-
  Oracle publishes NO OAuth scope registry for Siebel, and the absence is
  structural rather than an omission. Siebel is a resource server that never
  issues tokens: scope names are minted by whatever external OAuth provider the
  customer configures (Oracle Access Manager, IDCS/IAM, or a third party). All
  Oracle states is the matching rule — "if the token scope is used while
  retrieving the token, then the token scope must match the executed operation."
  There is consequently nothing for this artifact to enumerate, and enumerating
  plausible scope strings would fabricate a contract that does not exist.
finding: no-published-scope-registry
authorization_model:
  primary: siebel-responsibilities-positions-and-view-mode
  description: >-
    Real authorization in Siebel is data-level, not scope-level. The
    authenticated user's responsibilities, position and organization determine
    which records are visible, refined per request by the ViewMode query
    parameter. Two callers presenting tokens with identical scopes can legally
    see completely different data.
  scope_role: >-
    Where scopes exist at all, they are a coarse gate in front of Siebel, not a
    permission model inside it.
schemes:
  - name: oauth2
    declared_in:
      - openapi/oracle-siebel-accounts-api-openapi.yml
      - openapi/oracle-siebel-activities-api-openapi.yml
      - openapi/oracle-siebel-business-services-api-openapi.yml
      - openapi/oracle-siebel-contacts-api-openapi.yml
      - openapi/oracle-siebel-metadata-api-openapi.yml
      - openapi/oracle-siebel-opportunities-api-openapi.yml
      - openapi/oracle-siebel-orders-api-openapi.yml
      - openapi/oracle-siebel-products-api-openapi.yml
      - openapi/oracle-siebel-repository-api-openapi.yml
      - openapi/oracle-siebel-service-requests-api-openapi.yml
    declared_scopes: 0
    note: >-
      Every one of the ten specs declares an oauth2 scheme with an EMPTY scopes
      map. That is consistent with the documentation: there is no Siebel scope
      vocabulary to declare. The authorizationUrl and tokenUrl carried in those
      schemes are placeholders — Siebel exposes no such endpoints. See
      authentication/oracle-siebel-authentication.yml (spec_discrepancy).
mcp_scope_note: >-
  The Siebel AI Connectors MCP runtime does have a scope hook —
  security.jwt.required-scope in application.yaml — but the value is chosen by
  the deploying customer, so it too is deployment-specific rather than published.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set 
curl "https://apis.io/api/v1/scopes/oracle-siebel-scopes"
All oauth scopes 
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.