Set up a Blackline connector

C1 provides identity governance for Blackline. Integrate your Blackline instance with C1 for unified visibility and governance over user access.

This connector is in beta. This means it’s undergoing ongoing testing and development while we gather feedback, validate functionality, and improve stability. Beta connectors are generally stable, but they may have limited feature support, incomplete error handling, or occasional issues.

We recommend closely monitoring workflows that use this connector and contacting our Support team with any issues or feedback.

Capabilities

Resource	Sync	Provision
Account
Role
Team

Additional functionality:

None.

Gather Blackline configuration information

Configuring the connector requires you to pass in information from Blackline. Gather these configuration details before you move on.

Here’s the information you’ll need:

• Client ID
• Client Secret
• Username
• Password (API key)
• Scope
• Environment Subdomain

User must have an administrator role

Environment Subdomain is the BlackLine region used to build the API host https://{environment}.api.blackline.com (for example us, eu, or sbeu). This is the BlackLine region, not your company or instance name.

Scope must contain the API scope name(s) plus your instance identifier, entered as instance_<GUID> and separated by spaces — for example:

bl.users instance_00000000-0000-0000-0000-000000000000

The exact scope names and your instance GUID are unique to your instance and are provided by the BlackLine support team — enter the values BlackLine gives you rather than the placeholder above, and include a scope for each resource the connector syncs (users, teams, and roles). If the instance_<GUID> token is omitted, authentication fails with invalid_grant: Invalid instance GUID.

The connector uses the following endpoints:

• User management API
  • GET /v1/users
  • GET /v1/users/{id}/teams
• Team management API
  • GET /v1/teams
  • GET /v1/teams/{teamId}/users
• Role Management API
  • GET /v1/roles

View the documentation

Configure the Blackline connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Blackline configuration information gathered by following the instructions above

Cloud-hosted

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

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

2. Search for Blackline and click Add.

3. Choose how to set up the new Blackline 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 C1)
   • 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 C1 users. Setting multiple owners is allowed. If you choose someone else, C1 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 the configuration information from the previous section.

8. Click Save.

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

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

Self-hosted

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

Contact C1’s support team to download the latest version of the connector.

Step 1: Set up a new Blackline connector

1. In C1, navigate to Integrations > Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new Blackline 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 C1)
   • 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 C1 users. Setting multiple owners is allowed. If you choose someone else, C1 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 Blackline connector deployment:

Secrets configuration

# baton-blackline-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-blackline-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # Blackline config
  BATON_BLACKLINE_CLIENT_ID: <Client ID for your Blackline instance>
  BATON_BLACKLINE_CLIENT_SECRET: <Client Secret for your Blackline instance>
  BATON_BLACKLINE_ENVIRONMENT: <Environment where your Blackline instance is running (e.g. 'us' or 'eu')  See: https://developer.blackline.com/get-started>

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

Deployment configuration

# baton-blackline.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-blackline
  labels:
    app: baton-blackline
spec:
  selector:
    matchLabels:
      app: baton-blackline
  template:
    metadata:
      labels:
        app: baton-blackline
        baton: true
        baton-app: blackline
    spec:
      containers:
      - name: baton-blackline
        image: public.ecr.aws/conductorone/baton-blackline:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-blackline
        envFrom:
        - secretRef:
            name: baton-blackline-secrets

Step 3: Deploy the connector

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

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

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