ConductorOne provides identity governance and just-in-time provisioning for ZipHQ. Integrate your ZipHQ instance with ConductorOne 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.
Configuring the connector requires you to pass in information from ZipHQ. Gather these configuration details before you move on.Here’s the information you’ll need:
API Key
Base URL
To generate an API key in ZipHQ:
1
Click the gear icon at the top of Zip and select Company settings.
2
In the Company Settings menu on the left side of the page, click API.
3
To generate an API key, click + Create API key at the top right-hand corner of the page.
4
In the dropdown menu that appears, select Standard as type of API key.
5
In the Name field, enter a user-friendly name, such as conductorone-api-key.
6
Click Create and the Save API key token dialog will appear.
7
Click the copy button to the right of the displayed token to copy it to your clipboard, and the paste it in a secure location.
That’s it! Next, move on to the connector configuration instructions.
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of ZipHQ configuration information gathered by following the instructions above
Cloud-hosted
Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.
1
In ConductorOne, navigate to Admin > Connectors and click Add connector.
2
Search for ZipHQ and click Add.
3
Choose how to set up the new ZipHQ 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
4
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.
5
Click Next.
6
Find the Settings area of the page and click Edit.
7
Enter the configuration information from the previous section.
8
Click Save.
9
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 ZipHQ connector is now pulling access data into ConductorOne.
Follow these instructions to use the ZipHQ 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.
In ConductorOne, navigate to Connectors > Add connector.
2
Search for Baton and click Add.
3
Choose how to set up the new ZipHQ 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
4
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.
5
Click Next.
6
In the Settings area of the page, click Edit.
7
Click Rotate to generate a new Client ID and Secret.
Carefully copy and save these credentials. We’ll use them in Step 2.
# baton-ziphq-secrets.yamlapiVersion: v1kind: Secretmetadata: name: baton-ziphq-secretstype: OpaquestringData: # ConductorOne credentials BATON_CLIENT_ID: <ConductorOne client ID> BATON_CLIENT_SECRET: <ConductorOne client secret> # ZipHQ config BATON_BATON_ZIPHQ_API_KEY: <The API key for authenticating with ZipHQ> BATON_BATON_ZIPHQ_BASE_URL: <The base URL of the ZipHQ API> # 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.
Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
2
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 ZipHQ connector to. ZipHQ data should be found on the Entitlements and Accounts tabs.
That’s it! Your ZipHQ connector is now pulling access data into ConductorOne.
