Set up a Greenhouse connector

Capabilities

Resource	Sync	Provision
Accounts
Roles		See below

The Greenhouse connector supports automatic account provisioning. Note that newly provisioned accounts will be created with Basic user permissions. This connector does not support account deprovisioning. You must deprovision accounts directly in Greenhouse. The connector syncs roles, including roles for job permissions and future job permissions. Due to limitations of the Greenhouse API, this connector cannot provision all role assignments, but it can be used to revoke the Site Admin user permission from an account. You cannot revoke this permission from a non-human identity or from your own account.

Gather Greenhouse credentials

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

A user with the Site Admin user permission must complete this task.

Create a new Harvest API key

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

Click API Credential Management.

Click Create new API key and fill out the form:

API Type: Harvest
Partner: Custom integration
Description: C1 integration

Click Manage Permissions. The new key is generated.

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

Grant the API key permissions

On the next screen, select the relevant permissions:To give C1 READ (sync) permissions:

User roles - Get: List User Roles

To give C1 READ/WRITE (sync and provision) permissions:

User roles - All permissions
Users - All permissions

Click Save.

Done. Next, move on to the connector configuration instructions.

Configure the Greenhouse connector

To complete this task, you’ll need:

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

Cloud-hosted
Self-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

In C1, navigate to Apps > Connectors and click Add connector.

Search for Greenhouse and click Add.

Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

Find the Settings area of the page and click Edit.

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

Optional. If you’re using the Greenhouse connector to deprovision Site Admin user permissions, enter the email of a user with Site Admin permissions in the On behalf of field. This email address will be logged as the responsible party for the permission change in the Greenhouse audit log.

Click Save.

The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your Greenhouse connector is now pulling access data into C1.

Follow these instructions to use the Greenhouse connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

Resources

GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new Greenhouse connector

In C1, navigate to Apps > Connectors and click Add connector.

Search for Baton and click Add.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

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 Greenhouse connector deployment:

Secrets configuration

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

  # Optional: Include if you want C1 to provision access using this connector
  BATON_PROVISIONING: true

  # Optional: Include if you want to use C1 to deprovision Site Admin user permissions
  BATON_ON_BEHALF_OF_EMAIL: <Email of a user with Site Admin permissions, who will be logged as the responsible party>

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: public.ecr.aws/conductorone/baton-greenhouse:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-greenhouse
        envFrom:
        - secretRef:
            name: baton-greenhouse-secrets

Step 3: Deploy the connector

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

Check that the connector data uploaded correctly. In C1, click Apps. 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.

Done. Your Greenhouse connector is now pulling access data into C1.

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a Greenhouse connector

Capabilities

Gather Greenhouse credentials

Create a new Harvest API key

Grant the API key permissions

Configure the Greenhouse connector

Resources

Step 1: Set up a new Greenhouse connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Gather Greenhouse credentials

​Create a new Harvest API key

​Grant the API key permissions

​Configure the Greenhouse connector

​Resources

​Step 1: Set up a new Greenhouse connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Greenhouse credentials

Create a new Harvest API key

Grant the API key permissions

Configure the Greenhouse connector

Resources

Step 1: Set up a new Greenhouse connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector