Set up a BambooHR connector

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

A newer version of this connector is available. This version of the connector is no longer available for installation. If you’re setting up a BambooHR connector with ConductorOne for the first time, use the v2 version.

Capabilities

Resource	Sync	Provision
Accounts

Gather BambooHR credentials

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

1. Log into your BambooHR Administrator account.

2. Make a note of the company domain, which is found in the URL.

   
3. Next we’ll create a BambooHR API token. The user that creates the API token must be assigned an access level with these permissions:

   • Personal >> Basic Info >> Status - View Only
   • Personal >> Contact >> Work Email - View Only
   • Personal >> Basic Info >> First Name - View Only
   • Personal >> Basic Info >> Last Name - View Only
   • Job >> Job Information >> Reporting To - View Only
4. Click the BambooHR icon in the top right corner of the page and select API Keys.

   
5. On the API Keys page, select Add New Key.

   
6. Enter a name for your new key nd then click Generate Key.

   
7. Copy the newly generated API key.

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

Configure the BambooHR connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of BambooHR 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 BambooHR and click Add.

3. Choose how to set up the new BambooHR 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 company’s BambooHR domain into the Company domain field.

8. Paste the API key into the API key field.

9. Click Save.

10. 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 BambooHR connector is now pulling access data into ConductorOne.

Self-hosted

Follow these instructions to use the BambooHR 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 BambooHR connector

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

2. Search for Baton and click Add.

3. Choose how to set up the new BambooHR 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 BambooHR connector deployment:

Secrets configuration

# baton-bamboohr-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-bamboohr-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # BambooHR credentials
  BATON_API_KEY: <The API key generated for this integration>
  BATON_COMPANY_DOMAIN: <Your company's BambooHR domain>

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

Deployment configuration

# baton-bamboohr.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-bamboohr
  labels:
    app: baton-bamboohr
spec:
  selector:
    matchLabels:
      app: baton-bamboohr
  template:
    metadata:
      labels:
        app: baton-bamboohr
        baton: true
        baton-app: bamboohr
    spec:
      containers:
      - name: baton-bamboohr
        image: ghcr.io/conductorone/baton-bamboohr:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-bamboohr-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 BambooHR connector to. BambooHR data should be found on the Entitlements and Accounts tabs.

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