Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Bitbucket Data Center credentials

Each setup method requires you to pass in credentials generated in Bitbucket Data Center. 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 these permissions:

   • Group: Read
   • User: Read
   • Project: Read, Admin
   • Repository: Read, 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 Data Center 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 Data Center 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 Data Center 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 Data Center 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 Data Center connector deployment:

Secrets configuration

# baton-bitbucket-datacenter-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-bitbucket-datacenter-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Bitbucket Data Center credentials
  BATON_BITBUCKETDC_BASEURL: <Full URL of your Bitbucket Data Center Server (such as http://localhost:7990)>
  BATON_APP_PASSWORD: <Application password used to connect to the BitBucket API>
  BATON_USERNAME: <Username of Bitbucket administrator>

  # 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-datacenter.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-bitbucket-datacenter
  labels:
    app: baton-bitbucket-datacenter
spec:
  selector:
    matchLabels:
      app: baton-bitbucket-datacenter
  template:
    metadata:
      labels:
        app: baton-bitbucket-datacenter
        baton: true
        baton-app: bitbucket-datacenter
    spec:
      containers:
      - name: baton-bitbucket-datacenter
        image: ghcr.io/conductorone/baton-bitbucket-datacenter:latest
        args: ["service"]
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-bitbucket-datacenter-secrets

Step 3: Deploy the connector

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

   kubectl create namespace baton-bitbucket-datacenter
   

2. Apply the secret configuration:

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

3. Apply the deployment:

   kubectl -n baton-bitbucket-datacenter apply -f baton-bitbucket-datacenter.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-datacenter}
   

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 Data Center connector to. Bitbucket Data Center data should be found on the Entitlements and Accounts tabs.

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