Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Bitbucket credentials

Each setup method requires you to pass in credentials generated in Bitbucket. Gather these credentials before you move on.

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.

That’s it! Next, move on to the instructions for your chosen setup method.

Set up a Bitbucket cloud-hosted 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

1. In ConductorOne, click Connectors > 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 app password 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.

Set up a Bitbucket cloud-hosted connector using Terraform

As an alternative to the cloud-hosted setup 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.

Set up a Bitbucket self-hosted 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

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.

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the 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: <Application password used to connect to the BitBucket API>
  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
        args: ["service"]
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-bitbucket-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace baton-bitbucket
   

2. Apply the secret configuration:

   kubectl -n baton-bitbucket apply -f baton-bitbucket-secrets.yaml
   

3. Apply the deployment:

   kubectl -n baton-bitbucket apply -f baton-bitbucket.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n c1 get pods
   

2. View the connector logs:

   kubectl -n c1 logs -l app=baton-${baton-bitbucket}
   

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