Set up a Zuper connector

ConductorOne provides identity governance and just-in-time provisioning for Zuper. Integrate your Zuper instance with ConductorOne 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.

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

Log into Zuper Pro.
Navigate to Settings > Account Settings > API Keys.
Click New API Key.
Enter a name for your key, such as “ConductorOne”, and click Generate.
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.

That’s it! 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 ConductorOne
Access to the set of Zuper credentials generated by following the instructions above

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

In ConductorOne, navigate to Admin > Connectors and click Add connector.
Search for Zuper and click Add.
Choose how to set up the new Zuper 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 ConductorOne)
- Add the connector to a managed app (select from the list of existing managed apps)
- Create a new managed app
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
Find the Settings area of the page and click Edit.
Enter the Base API URL in the API URL field.
Enter the API key in the API key field.
Click Save.
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your Zuper connector is now pulling access data into ConductorOne.

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 ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Step 1: Configure the Zuper connector

In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new Zuper 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 ConductorOne)
- Add the connector to a managed app (select from the list of existing managed apps)
- Create a new managed app
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
In the Settings area of the page, click Edit.
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 Zuper connector deployment:

Secrets configuration

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

  # Optional: include if you want ConductorOne 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: ghcr.io/conductorone/baton-zuper:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-zuper-secrets

Step 3: Deploy the connector

Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
Check that the connector data uploaded correctly. In ConductorOne, click Applications. 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.

That’s it! Your Zuper connector is now pulling access data into ConductorOne.