Set up IBM Blueworks Live connector

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

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
Group
License
Space

Additional functionality:

Supports automatic account provisioning and deprovisioning

Gather Blueworks Live configuration information

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

Here’s the information you’ll need:

• Client ID
• Client Secret
• Region
• Spaces Tag

See the Blueworks Live docs for information on how to acquire credentials: View the documentation

This connector requires the following scopes:

• Artifact reporting
• User management

Learn how to set the scopes

Configure the Blueworks Live connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Blueworks Live 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 Apps > Connectors and click Add connector.

2. Search for Blueworks Live and click Add.

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

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

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

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

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

8. Enter the configuration information from the previous section.

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.

Done. Your Blueworks Live connector is now pulling access data into C1.

Self-hosted

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

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

2. Search for Baton and click Add.

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

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

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

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

7. In the Settings area of the page, click Edit.

8. 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 Blueworks Live connector deployment:

Secrets configuration

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

  # Blueworks Live config
  BATON_BLUEWORKS_LIVE_CLIENT_ID: <Client ID for Blueworks Live>
  BATON_BLUEWORKS_LIVE_CLIENT_SECRET: <Client Secret for Blueworks Live>
  BATON_BLUEWORKS_LIVE_REGION: <Region for Blueworks Live>
  BATON_BLUEWORKS_LIVE_SPACES_TAG: <Tag for Blueworks Live spaces>

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

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

Deployment configuration

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

Done. Your Blueworks Live connector is now pulling access data into C1.