Set up a Bitbucket connector

ConductorOne provides identity governance for Bitbucket. Integrate your Bitbucket instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.

Capabilities

Resource	Sync	Provision
Accounts
Workspaces
Groups
Projects
Repositories

Gather Bitbucket credentials

Configuring the connector requires you to pass in credentials generated in Bitbucket. Gather these credentials before you move on.

Create an API token

1. In Bitbucket, navigate to your account’s API Tokens page.

2. Click Create API token with scopes.

3. Give the API token a name, such as “ConductorOne”, and set its expiration date.

4. Select Bitbucket from the list of apps.

5. On the Select Bitbucket scopes page, select the following:

   Read scopes:

   • read:workspace:bitbucket - Required to read workspace details and workspace members
   • read:user:bitbucket - Required to read user information
   • read:project:bitbucket - Required to read project information
   • read:repository:bitbucket - Required to read repository information

   Admin scopes:

   • admin:workspace:bitbucket - Required to read workspace user groups (v1.0 API) and manage group memberships
   • admin:project:bitbucket - Required to read and manage project permissions for users and groups
   • admin:repository:bitbucket - Required to read and manage repository permissions for users and groups
6. Click Next.

7. Review your new API token’s details and click Create token.

8. Carefully copy and save the API token.

That’s it! Next, move on to the connector configuration instructions.

Configure the Bitbucket connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Bitbucket credentials generated by following the instructions above

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.

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

2. Search for Bitbucket and click Add.

3. Choose how to set up the new Bitbucket connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
   • Add the connector to a managed app (select from the list of existing managed apps)
   • Create a new managed 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. If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

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

7. Enter your Bitbucket username into the Username field.

8. Enter the API token created for this integration into the App password field.

9. 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.

10. Click Save.

11. 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.

Self-hosted

Follow these instructions to use the Bitbucket connector, hosted and run in your own environment.

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Step 1: Set up a new Bitbucket connector

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new Bitbucket connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
   • Add the connector to a managed app (select from the list of existing managed apps)
   • Create a new managed 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. If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. Click Rotate to generate a new Client ID and Secret. Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Bitbucket connector deployment:

Secrets configuration

# baton-bitbucket-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-bitbucket-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Bitbucket credentials
  BATON_APP_PASSWORD: <Bitbucket API token>
  BATON_USERNAME: <Username of administrator>
  BATON_WORKSPACES: <Workspace slugs of the workspaces to sync (if not specified, all workspaces will sync)>

  # Optional: include if you want ConductorOne to provision access using this connector
  BATON_PROVISIONING: true

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-bitbucket.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-bitbucket
  labels:
    app: baton-bitbucket
spec:
  selector:
    matchLabels:
      app: baton-bitbucket
  template:
    metadata:
      labels:
        app: baton-bitbucket
        baton: true
        baton-app: bitbucket
    spec:
      containers:
      - name: baton-bitbucket
        image: ghcr.io/conductorone/baton-bitbucket:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-bitbucket
        envFrom:
        - secretRef:
            name: baton-bitbucket-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.

2. Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the Bitbucket connector to. Bitbucket data should be found on the Entitlements and Accounts tabs.

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