Set up Zscaler ZIdentity connector

C1 provides identity governance and just-in-time provisioning for Zscaler ZIdentity. Integrate your Zscaler ZIdentity 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 the C1 Support team with any issues or feedback.

Capabilities

Resource	Sync	Provision
Account
Group

Additional functionality:

Supports automatic account provisioning

This connector does not support account deprovisioning. You must deprovision accounts directly in Zscaler ZIdentity.

When a new account is created by C1, the account’s password will be sent to a vault.

Gather Zscaler ZIdentity configuration information

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

Here’s the information you’ll need:

• Zscaler ZIdentity Base URL
• Zscaler ZIdentity Client ID
• Zscaler ZIdentity Client Secret

See the Zscaler ZIdentity docs for information on how to acquire credentials: View the documentation

Configure the Zscaler ZIdentity connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Zscaler ZIdentity 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 Zscaler ZIdentity 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 Zscaler ZIdentity connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the Zscaler ZIdentity 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 Zscaler ZIdentity 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 Zscaler ZIdentity connector deployment:

Secrets configuration

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

  # Zscaler ZIdentity config
  BATON_ZSCALER_ZIDENTITY_BASE_URL: <Zscaler ZIdentity Base URL>
  BATON_ZSCALER_ZIDENTITY_CLIENT_ID: <Zscaler ZIdentity Client ID>
  BATON_ZSCALER_ZIDENTITY_CLIENT_SECRET: <Zscaler ZIdentity Client Secret>

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

Done. Your Zscaler ZIdentity connector is now pulling access data into C1.