Set up a Bitbucket Data Center connector

Capabilities
Gather Bitbucket Data Center credentials
Create an HTTP token
Configure the Bitbucket Data Center connector

Capabilities

Resource	Sync	Provision
Accounts
Projects
Repositories
Groups
Organizations

Gather Bitbucket Data Center credentials

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

Create an HTTP token

In Bitbucket, click your profile in the top right corner of the screen and navigate to Manage account > HTTP access tokens.

Click Create token.

Give the token a name, such as “ConductorOne”.

In the Permissions section of the page, select these permissions:

Project: Admin
Repository: Admin

Click Create.

Your new token is shown. Carefully copy and save the token.

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

Configure the Bitbucket Data Center 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

Cloud-hosted
Self-hosted

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

Follow these instructions to use the Bitbucket Data Center, 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 Data Center connector

In ConductorOne, navigate to Connectors > Add connector.

Search for Baton and click Add.

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

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.

Click Next.

In the Settings area of the page, click Edit.

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_BITBUCKETDC_TOKEN: <Bitbucket HTTP access token>
  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
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-bitbucket-datacenter
        envFrom:
        - secretRef:
            name: baton-bitbucket-datacenter-secrets

Step 3: Deploy the connector

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

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.

Set up a Bitbucket connector

Set up a Confluence connector

⌘I

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

Set up a Bitbucket Data Center connector

Capabilities

Gather Bitbucket Data Center credentials

Create an HTTP token

Configure the Bitbucket Data Center connector

Step 1: Set up a new Bitbucket Data Center connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

​Capabilities

​Gather Bitbucket Data Center credentials

​Create an HTTP token

​Configure the Bitbucket Data Center connector

​Step 1: Set up a new Bitbucket Data Center connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Bitbucket Data Center credentials

Create an HTTP token

Configure the Bitbucket Data Center connector

Step 1: Set up a new Bitbucket Data Center connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector