Set up a Zuper connector

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

Capabilities

Resource	Sync	Provision
Accounts
Roles
Access roles
Teams

The Zuper connector supports automatic account provisioning.

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

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

Gather Zuper credentials

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

Generate an API key

1. Log into Zuper Pro.

2. Navigate to Settings > Account Settings > API Keys.

3. Click New API Key.

4. Enter a name for your key, such as “C1”, and click Generate.

5. Carefully copy and save the API key.

Look up your API URL

Make the following HTTP call to the Zuper Pro API to look up your Base API URL:

curl 'https://accounts.zuperpro.com/api/config' \
-H 'content-type: application/json;charset=UTF-8' \
--data-raw '{"company_name":"your-company-login-name"}' \
--compressed

The call’s response will look like this:

{
    "type": "success",
    "config": {
        "dc_name": "us-west-1c",
        "dc_provider": "AWS",
        "dc_country": "US WEST",
        "dc_api_url": "https://us-west-1c.zuperpro.com",
        "dc_socket_url": "https://us-west-1c.zuperpro.com:8443",
    }
}

The dc_api_url in the response is your Zuper account’s BASE API URL.

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

Configure the Zuper connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Zuper 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 Zuper 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 Base API URL in the API URL field.

9. Enter the API key in the API key field.

10. Click Save.

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

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

Self-hosted

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

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

Step 1: Configure the Zuper 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.

9. 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 Zuper connector deployment:

Secrets configuration

# baton-zuper-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-zuper-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Zuper credentials
  BATON_API_URL: <Zuper Base API URL>
  BATON_API_KEY: <Zuper API key>

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

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