Availability

✅ General availability. The Bitbucket connector is available to all ConductorOne users.

Capabilities

• Sync user identities from Bitbucket to ConductorOne

• Resources supported:

  • Workspaces
  • Groups
  • Projects
  • Repositories

• Provisioning supported:

  • Groups

Add a new Bitbucket connector

This task requires either the Connector Administrator or Super Administrator role in ConductorOne.

1. In ConductorOne, open Admin and click Connectors > Add connector.

2. Search for Bitbucket and click Add.

3. Choose whether to add the new Bitbucket connector as a data source to an existing application (and select the app of your choice) or to create a new application.

   Do you SSO into Bitbucket using your identity provider (IdP)? If so, make sure to add the connector to the Bitbucket app that was created automatically when you integrated your IdP with ConductorOne, rather than creating a new app.

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   A Bitbucket connector owner must have the following permissions:

   • Connector Administrator or Super Administrator role in ConductorOne
   • Permission to create an OAuth consumer for the Bitbucket Cloud workspace you’re integrating

5. Click Next.

Next steps

• If you are the connector owner, proceed to Configure your Bitbucket connector for instructions on integrating Bitbucket with ConductorOne.

• If someone else is the connector owner, ConductorOne will notify them by email that their help is needed to complete the setup process.

Configure your Bitbucket connector

A user with the Connector Administrator or Super Administrator role in ConductorOne and the permission to create an app password in Bitbucket must perform this task.

Step 1: Create an app password

1. In Bitbucket, click Settings (gear icon) in the top right corner of the screen and then click Personal settings > Personal Bitbucket settings.

2. In the menu on the left side of the page, click App passwords.

3. Click Create app password.

4. Give the password a name, such as “ConductorOne”.

5. In the Permissions section of the page, select the relevant set of permissions:

   To run access reviews on your Bitbucket users:

   • Account: Read
   • Workspace membership: Read
   • Projects: Read, Admin
   • Repositories: Admin

   To provision Bitbucket group membership via ConductorOne and run access reviews:

   • Account: Read, Write
   • Workspace membership: Read
   • Projects: Read, Admin
   • Repositories: Admin

6. Click Create.

7. Your new password is shown. Carefully save the password. We’ll use it in Step 2.

Step 2: Add your Bitbucket credentials to ConductorOne

1. In ConductorOne, navigate to the Bitbucket connector by either:

   • Clicking the Set up connector link in the email you received about configuring the connector.

   • Navigate to Admin > Connectors > Bitbucket (if there is more than one Bitbucket listed, click the one with your name listed as owner and the status Not connected).

2. Find the Settings area of the page and click Edit.

3. Enter your Bitbucket username into the Username field.

4. Enter the password you created in Step 1 into the App password field.

5. Optional. Enter the names of the specific Bitbucket workspaces you want to integrate. If you have only one workspace, or if you want to integrate all your workspaces, you do not need to enter anything here.

6. Click Save.

7. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your Bitbucket connector is now pulling access data into ConductorOne.

Configure the Bitbucket integration using Terraform

As an alternative to the integration process described above, you can use Terraform to configure the integration between Bitbucket and ConductorOne.

See the ConductorOne Bitbucket integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.