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.
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
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.