Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Greenhouse credentials

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

A user with the Can manage ALL organization’s API Credentials permission must complete this task.

Create a new Harvest API key

1. In Greenhouse, click Configure (the gear icon) and select Dev Center.

2. Click API Credential Management.

3. Click Create new API key and fill out the form:

   • API Type: Harvest
   • Partner: Custom integration
   • Description: ConductorOne integration

4. Click Manage Permissions. The new key is generated.

5. Carefully copy and save the API key, then click I have stored the API Key.

Grant the API key permissions

1. On the next screen, select the following permissions:

   • Users - Get: List Candidates
   • User roles - Get: List User Roles

2. Click Save.

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

Set up a Greenhouse cloud-hosted connector

To complete this task, you’ll need:

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

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

2. Search for Greenhouse and click Add.

   Don’t see the Greenhouse connector? Reach out to support@conductorone.com to add Greenhouse to your Connectors page.

1. Choose how to set up the new Greenhouse 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

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

3. Click Next.

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

5. Paste your Greenhouse API token into the Greenhouse Username (API Token) field. (Greenhouse uses API tokens as usernames when authenticating.)

6. Click Save.

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

Set up a Greenhouse self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Greenhouse 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 Greenhouse connector

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

2. Search for Baton and click Add.

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

Secrets configuration

# baton-greenhouse-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-greenhouse-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Greenhouse credentials
  BATON_USERNAME: <Your Greenhouse API token (Greenhouse uses API tokens as usernames when authenticating)>

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

Deployment configuration

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

Step 3: Deploy the connector

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

   kubectl create namespace conductorone
   

2. Apply the secret configuration:

   kubectl -n conductorone apply -f baton-greenhouse-secrets.yaml
   

3. Apply the deployment:

   kubectl -n conductorone apply -f baton-greenhouse.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n conductorone get pods
   

2. View the connector logs:

   kubectl -n conductorone logs -l app=baton-${baton-greenhouse}
   

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

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