Bitbucket connects through OAuth. As with GitLab, a connected repository is scanned, read, and fixed exactly like a GitHub one.
Connect a workspace
- 1Open the repositories page
Go to cefense.com/app and choose Bitbucket.
- 2Authorise
Bitbucket asks you to grant access. Signing in happens on Bitbucket.
- 3Connect a repository
The repositories your account can reach are listed. Connecting one queues its first scan.
Repository access
Cefense sees what your Bitbucket account can see, across the workspaces you belong to. Losing access to a repository in Bitbucket removes it here as well.
What works, and the one thing that is GitHub only
| Capability | Bitbucket |
|---|---|
| Scanning, findings, branches, commits | Yes |
| Fix generation, pull requests, and merging | Yes |
| Connecting a repository from the workspace | Yes |
Connecting a repository with cf repo connect --provider bitbucket | Yes |
| Authorising the Bitbucket account itself | In a browser, as with every host |
cf scan --url | GitHub only. Connect the repository, then cf scan. |
Troubleshooting
A repository is missing
Check that your Bitbucket account has access to it, then disconnect and reconnect the account so Cefense refreshes the list.
The connection stopped working
Reconnect from the workspace. A revoked authorisation cannot be renewed silently.
Have a correction or need help?
Email the docs team