Set up a PrivX connector

C1 provides identity governance for PrivX. Integrate your PrivX 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
Accounts
Roles

Gather PrivX credentials

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

A user with the Admin role in PrivX must perform this task.

Set up a PrivX role

First, create a PrivX role that will be used to grant permissions to the API client you’ll use to integrate with C1.

1. In PrivX, navigate to Administration > Roles and click Add Role.

2. Create a new role (or locate an existing role) with the following permissions:

   • roles-view
   • users-view
   • role-target-resources-view
3. Make a note of the name of the role.

Create a PrivX API client

1. Still in PrivX, navigate to Administration > Deployment and click Integrate with PrivX Using API Clients.

2. Click Add API Client.

3. Give the new client a name and assign it the role you just created or identified.

4. Click Save.

5. Scroll down to the Credentials section of the page. Carefully copy and save the OAuth Client ID and Client Secret, and the API Client ID and Client Secret.

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

Configure the PrivX connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of PrivX credentials generated 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 PrivX 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. Select your preferred authentication method, OAuth or Client secret:

   • For OAuth, enter your PrivX base URL and paste in the OAuth credentials.

   • For Client secret, enter your PrivX base URL and paste in the API client credentials.

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

Self-hosted

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

• Official download center: For stable binaries (Windows/Linux/macOS) and container images.

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

Step 1: Set up a new PrivX 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 PrivX connector deployment:

Secrets configuration

# baton-privx-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-privx-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # PrivX credentials, option 1
  BATON_API_CLIENT_ID: <PrivX API client ID>
  BATON_API_CLIENT_SECRET: <PrivX API client secret>
  BATON_BASE_URL: <PrivX instance base URL>

  # PrivX credentials, option 2
  BATON_OAUTH_CLIENT_ID: <PrivX OAuth client ID>
  BATON_OAUTH_CLIENT_SECRET: <PrivX OAuth client secret>
  BATON_BASE_URL: <PrivX instance base URL>

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

Deployment configuration

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

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