Reference A: Authorization scopes and subscribed events

Review the OAuth scopes and Bitbucket Cloud events required for the integration.

Cortex Cloud uses OAuth 2.0 for Bitbucket Cloud integrations. The requested scopes allow repository discovery, scanning, and event subscriptions.

OAuth scopes

• project: View projects. This scope also implies repository read access for repositories in those projects.
• repository: Read repository contents and metadata.
• repository:write: Write repository access. This scope implies repository.
• pullrequest: Read pull requests and create, resolve, and comment on tasks.
• pullrequest:write: Create, merge, decline, and approve pull requests. This scope also implies pullrequest and repository:write.
• issue: View, list, search, create, comment on, watch, and vote on issues.
• issue:write: Transition and delete issues. This scope implies issue.
• webhook: View and manage webhook subscriptions. Creating a webhook also requires read access to its resource.
• snippet: Read snippets and create snippet comments.
• email: View the user's primary email address.
• account: View user account details and workspace users, permissions, and projects.
• pipeline: Read pipelines, steps, deployment environments, and variables.
• pipeline:write: Stop, rerun, resume, and manually trigger pipelines.

For more information, see the Bitbucket authentication documentation.

Personal Access Tokens (PATs) are not supported. Cortex Cloud refreshes OAuth tokens automatically.

Subscribed events

Cortex Cloud subscribes to these events to keep repository and pull request data current:

• repo:push
• repo:fork
• repo:updated
• repo:commit_comment_created
• repo:commit_status_created
• repo:commit_status_updated
• issue:created
• issue:comment_created
• issue:updated
• pullrequest:created
• pullrequest:updated
• pullrequest:fulfilled
• pullrequest:rejected