OpenText Cybersecurity · OAuth Scopes

OpenText Cybersecurity OAuth Scopes

OAuth 2.0 derived

OpenText Cybersecurity 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.

CybersecurityApplication SecurityVulnerability ManagementSASTDASTEndpoint SecurityThreat DetectionEmail SecurityBackup and RecoveryManaged Service ProvidersIdentity and AccessData PrivacyEnterprise Software
Scopes: 0 Flows: Method: derived

Scopes (0)

OpenText Cybersecurity 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.

derive-oauth-scopes.py returns nothing for this provider because the Swagger document declares no oauth2 securityDefinition to read the scopes from (see authentication/). The scopes are nevertheless fully published — one per operation, in the operation's own description — so they are recovered here by parsing those descriptions. Counts are operation counts, not guesses.

Source

OAuth Scopes

Raw ↑
generated: '2026-09-13'
method: derived
source: >-
  openapi/opentext-cybersecurity-fortify-on-demand-openapi.json — every operation description carries an
  "Allowed Scopes:" line; the scope vocabulary below was extracted from all 159 operations. Cross-checked
  against https://unityapi.webrootcloudav.com/Docs/en/APIDoc/Guide for the Webroot Unity scope vocabulary,
  which is documented on a public page.
note: >-
  derive-oauth-scopes.py returns nothing for this provider because the Swagger document declares no
  oauth2 securityDefinition to read the scopes from (see authentication/). The scopes are nevertheless
  fully published — one per operation, in the operation's own description — so they are recovered here
  by parsing those descriptions. Counts are operation counts, not guesses.
apis:
- api: opentext-cybersecurity:fortify-on-demand-api
  token_url: https://api.ams.fortify.com/oauth/token
  scope_parameter_required: true
  scopes:
  - name: api-tenant
    operations: 150
    description: >-
      The broad tenant-administration scope. Present on almost every operation in the contract, including
      all of API key management, attributes, audit templates, DAST/dynamic/static/mobile scans, and tenant
      summary and heat-map reads.
  - name: start-scans
    operations: 28
    description: Start static, dynamic, mobile, open-source and DAST-automated scans on a release.
  - name: view-apps
    operations: 21
    description: Read applications, releases and scan metadata.
  - name: view-issues
    operations: 21
    description: Read vulnerabilities and open-source components on a release.
  - name: manage-apps
    operations: 14
    description: Create, update and delete applications, releases, attributes and microservices.
  - name: manage-issues
    operations: 8
    description: Audit and triage vulnerabilities; manage audit templates.
  - name: view-reports
    operations: 8
    description: Read generated reports and scan summaries.
  - name: view-tenant-data
    operations: 11
    description: Read tenant entitlements, event logs, lookup items, FoD Connect networks and attributes.
  - name: manage-users
    operations: 11
    description: Create and modify users, user groups and their application access.
  - name: view-users
    operations: 4
    description: Read users, user groups and their application access.
  - name: manage-notifications
    operations: 3
    description: Manage notification settings.
  - name: manage-reports
    operations: 3
    description: Create and delete reports.
  - name: manage-user
    operations: 2
    description: >-
      Singular variant appearing on two UserManagement operations. Recorded verbatim; the docs do not
      say whether this is distinct from manage-users or a spelling inconsistency in the contract.
  findings:
  - id: scope-string-typo-in-contract
    detail: >-
      One Scans operation's description reads "Allowed Scopes: view-apps</remarks>" — a leaked XML doc
      comment tag. The intended scope is view-apps. Recorded because it shows the scope list is generated
      from source comments and is not validated.
- api: opentext-cybersecurity:webroot-unity-api
  token_url: https://unityapi.webrootcloudav.com/auth/token
  docs: https://unityapi.webrootcloudav.com/Docs/en/APIDoc/Guide
  method: searched
  scope_pattern: '[extensionName].[domain]'
  wildcards:
    supported: true
    forms:
    - '[extensionName].* — all scopes for an extension, e.g. SkyStatus.*'
    - '*.[domain] — all scopes for a domain, e.g. *.GSM'
    - '* — all scopes available to the user'
    not_supported_for: Identity Provider flows (authorization code and token exchange)
  scopes:
  - name: ECom.Shop
    path_prefix: /service/api/ecom/shop
    description: Create and modify licenses; retrieve license and license-order information.
  - name: SkyStatus.GSM
    path_prefix: /service/api/status/gsm
    description: Agent and license status across a Global Site Manager console.
  - name: SkyStatus.Site
    path_prefix: /service/api/status/site
    description: Agent and license status for a single site.
  - name: SkyStatus.Reporting
    path_prefix: /service/api/status/reporting
    description: Usage reporting across endpoint, DNS Protection, WSAT, Pillr, Detection and Response, OTSB and CloudAlly.
  - name: Console.Access
    path_prefix: /service/api/console/access
    description: Console access operations.
  - name: Console.GSM
    path_prefix: /service/api/console/gsm
    description: >-
      Site, user, policy, endpoint, endpoint-group and endpoint-command management on a GSM console.
      Granted by default to every GSM console user; some operations additionally require the GSM Super
      Admin account type.
  - name: Notifications.Subscriptions
    path_prefix: /service/api/notifications/subscriptions
    description: >-
      Event-notification subscriptions. NOT granted automatically — it must be enabled on the client
      credentials in the GSM console (Settings -> API Access) or requested from a Webroot representative.
  - name: SecureCloud.Platform
    path_prefix: /service/api/securecloud/customers
    description: OpenText Secure Cloud customer records.
  - name: SecureCloud.Usage
    path_prefix: /service/api/securecloud/usage/charges
    description: OpenText Secure Cloud usage and charges.
  guidance: >-
    The documentation advises requesting the minimum set of scopes, because there is a per-scope
    performance overhead on token issuance.

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/opentext-cybersecurity-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.

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