Bitbucket integration¶
Connect DXDT to Bitbucket Cloud with read-only access so the platform can correlate incidents against recent commits, pull requests, and Pipelines (CI/CD) runs. DXDT only reads.
| Setup time | ~8 minutes |
| Difficulty | Easy |
Access required: Bitbucket user with read access to the workspace repositories
Prerequisites¶
- A Bitbucket Cloud account with access to the target workspace
- Read access to the repositories DXDT should query
- Your workspace ID
Setup¶
1. Open App passwords¶
Sign in to Bitbucket, then go to Personal settings → App passwords and click Create app password. Label it DXDT.
- Avatar → Personal settings
- Open App passwords
- Click Create app password
2. Grant read-only scopes¶
Select only read permissions: Account: Read, Repositories: Read, Pull requests: Read, and Pipelines: Read. Do not grant any write or admin scopes. Create the app password and copy it — it is shown only once.
Note
Least privilege: read scopes are all DXDT needs.
3. Identify your username and workspace¶
Your username is your Bitbucket username (not your email address). Your workspace is the workspace ID as it appears in your repo URLs, bitbucket.org/<workspace>/....
Note
Using the email instead of the username is the most common setup error.
4. Enter the values in DXDT¶
In the plugin Configuration tab, paste Username, App Password, and Workspace and save. DXDT validates with a read-only ping.
Configuration fields¶
| Field | Where to find it |
|---|---|
Username (username) |
Your Bitbucket username (from Personal settings → Account), not your email. |
App Password (app_password) |
The value from Create app password with read-only scopes. |
Workspace (workspace) |
The workspace ID shown in your repo URLs: bitbucket.org/<workspace>/. |
Verify the connection¶
Save on the Configuration tab and confirm the Live Status panel is healthy; DXDT runs a read-only ping verifying workspace access, then can list repos.
Security
Credentials are stored encrypted per-tenant and used only for read-only Bitbucket calls.
Troubleshooting¶
401/403 on save
Wrong username (email used instead), or the app password lacks the read scopes. Use the Bitbucket username and recreate the app password with Account/Repositories/Pull requests/Pipelines read.
No repositories listed
The user has no access to repositories in that workspace. Grant the user read access to the repos, or verify the workspace ID is correct.
Workspace not found
Incorrect workspace value. Copy the exact workspace ID from a repository URL.
Vendor documentation: https://support.atlassian.com/bitbucket-cloud/docs/create-an-app-password/