Set up Airbyte connector

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

Capabilities

Resource	Sync	Provision
Accounts
Organizations
Workspaces

Gather Airbyte credentials

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

Create an application

1. In the Airbyte UI, navigate to Settings > Account > Applications and click Create an application.

2. Give your application a name, such as “ConductorOne”, then click Submit.

3. The application is created. Carefully copy and save the application client ID and client secret.

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

Configure the Airbyte connector

To complete this task, you’ll need:

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

3. Choose how to set up the new Airbyte 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 Airbyte hostname (in https://cloud.airbyte.com format) into the Airbyte hostname field.

8. Paste your client ID and client secret into the relevant fields.

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

Self-hosted

Follow these instructions to use the Airbyte 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: Configure the Airbyte connector

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

2. Search for Baton and click Add.

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

Secrets configuration

# baton-airbyte-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-airbyte-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Airbyte credentials
  BATON_AIRBYTE_CLIENT_ID: <Airbyte client ID>
  BATON_AIRBYTE_CLIENT_SECRET: <Airbyte client secret>
  BATON_DOMAIN_URL: <URL of your Airbyte instance, such as https://cloud.airbyte.com>

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

Deployment configuration

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

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