Availability

This connector works with Zoom on the Pro, Business, Business Plus, or Enterprise plan. The Zoom Basic plan is not supported.

Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Zoom credentials

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

A user with Account Owner status in Zoom must perform this task.

Create a Zoom OAuth app

1. Navigate to the Zoom App Marketplace.

2. Click Develop and select Build App.

3. Locate the Server-to-Server OAuth option and click Create.

4. Give your app a name, such as “ConductorOne” and click Create.

5. A page for the newly created app opens. Copy and save the Account ID, Client ID, and Client secret shown on this page.

Configure and activate the OAuth app

1. From the App Credentials page, click Continue.

2. On the Basic information page, fill out the form and click Continue.

3. On the Feature page, do not make any changes. Click Continue.

4. On the Scopes page, click + Add Scopes. Give the app the following set of scopes:

   • contact_group:read:list_groups:admin
   • group:read:list_groups:admin
   • group:read:list_members:admin
   • group:read:administrator:admin
   • role:read:list_roles:admin
   • role:read:list_members:admin
   • user:read:user:admin
   • user:read:list_users:admin

   If you want to use ConductorOne to provision and deprovision Zoom permissions, add these scopes as well:

   • role:write:member:admin
   • role:delete:member:admin
   • group:write:member:admin
   • group:delete:member:admin

5. Click Done. Review the list of scopes and click Continue.

6. On the Activation page, click Activate your app.

That’s it! Next, move on to the instructions for your chosen setup method.

Set up a Zoom cloud-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Zoom credentials generated by following the instructions above

1. In ConductorOne, click Connectors > Add connector.

2. Search for Zoom and click Add.

3. Choose how to set up the new Zoom 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 account ID for the new app into the Account ID fields.

8. Enter the Client ID and Client secret into the Client ID and Client secret fields.

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.

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

Set up a Zoom cloud-hosted connector using Terraform

As an alternative to the cloud-hosted setup process described above, you can use Terraform to configure the integration between Zoom and ConductorOne.

See the ConductorOne Zoom integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.

Set up a Zoom self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Zoom credentials generated by following the instructions above

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.

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the Zoom connector

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new Zoom 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.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Zoom connector deployment:

Secrets configuration

# baton-zoom-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-zoom-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Zoom credentials
  BATON_ACCOUNT_ID: <Zoom app account ID>
  BATON_ZOOM_CLIENT_ID: <Zoom client ID>
  BATON_ZOOM_CLIENT_SECRET: <Zoom client secret>

  # 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-zoom.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-zoom
  labels:
    app: baton-zoom
spec:
  selector:
    matchLabels:
      app: baton-zoom
  template:
    metadata:
      labels:
        app: baton-zoom
        baton: true
        baton-app: zoom
    spec:
      containers:
      - name: baton-zoom
        image: ghcr.io/conductorone/baton-zoom:latest
        args: ["service"]
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-zoom-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace baton-zoom
   

2. Apply the secret configuration:

   kubectl -n baton-zoom apply -f baton-zoom-secrets.yaml
   

3. Apply the deployment:

   kubectl -n baton-zoom apply -f baton-zoom.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n c1 get pods
   

2. View the connector logs:

   kubectl -n c1 logs -l app=baton-${baton-zoom}
   

3. 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 Zoom connector to. Zoom data should be found on the Entitlements and Accounts tabs.

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