Creating a Zoom connection - PingOne Cloud Platform - PingOne

PingOne Cloud Platform

bundle
pingone
ft:publication_title
PingOne Cloud Platform
Product_Version_ce
PingOne Cloud Platform
PingOne
category
Administratorguide
ContentType
Guide
Product
Productdocumentation
p1
p1cloudplatform
ContentType_ce
Guide
Product documentation
Guide > Administrator Guide

Use a Zoom connection to enable provisioning from PingOne to the Zoom user directory.

We recommend that you review the Zoom documentation, including:

Make sure that you have:
  • A Zoom system administrator account.
  • The Account ID, Client ID, and Client secret for a Server-to-Server OAuth application or the API key and API secret for a JWT application. For more information, see Creating an application in Zoom.
    Note:

    Zoom has deprecated the JWT app type. You should create new apps of Server-to-Server OAuth type. For more information, see the JWT App Type Deprecation FAQ in the Zoom documentation.

  1. Go to Integrations > Provisioning.
  2. Click the + icon and then click New Connection.
  3. For Identity Store, click the Select button.
  4. Under Zoom, click Select and then click Next.
  5. Enter a name and description for this provisioning connection. The connection name will appear in the list when you've completed and saved the connection.
  6. Click Next.
  7. On the Configure authentication screen, enter the following information. For information about finding these values, see Creating an application in Zoom.
    • SCIM URL. The fully qualified URL for the SCIM resource, such as https://api.zoom.us/scim2.
    • Authentication Method. Select one of the available authentication methods: OAuth Bearer Token for Server-to-Server OAuth applications or JWT Bearer Token for JWT applications. The configuration fields will change appropriately.
    • OAuth Token URL (OAuth only). The fully qualified URL for the token resource, such as https://zoom.us/oauth/token.
    • OAuth Account ID (OAuth only). The account ID to identify the connected Server-to-Server OAuth application in Zoom.
    • OAuth Client ID (OAuth only). The client ID to identify the connected Server-to-Server OAuth application in Zoom.
    • OAuth Client Secret (OAuth only). The credentials for the connected Server-to-Server OAuth application in Zoom.
    • API Key (JWT only). The key to identify the connected application in Zoom.
    • API Secret (JWT only). The credentials for the connected application in Zoom.
  8. Click Test connection to verify that PingOne can establish a connection to Zoom. If there are any issues with the connection, a Test connection failed message will appear. Click Continue to resume the setup with an invalid connection. You will not be able to use the connection for provisioning until you have established a valid connection to Zoom. Click Cancel to modify the settings and try again.
  9. On the Actions screen, enter the following:
    • Allow users to be created. Determines whether to create a user in the Zoom user directory when the user is created in the PingOne identity store.
    • Allow users to be updated. Determines whether to update user attributes in the Zoom user directory when the user is updated in the PingOne identity store.
      • Allow users to be disabled. When a user is disabled in the PingOne identity store, PingOne disables the user in the external identity store.
    • Allow users to be deprovisioned. Determines whether to deprovision a user in the Zoom user directory when the user is deprovisioned in the PingOne identity store.
    • Remove action. Determines the action to take when removing a user from the Zoom user directory.
      • Disable. When a user is deprovisioned from the PingOne identity store, PingOne disables the user in the external identity store.
      • Delete. When a user is deprovisioned from the PingOne identity store, PingOne deletes the user in the external identity store.
    • Deprovision on rule deletion. Determines whether to deprovision users that were provisioned using this rule if the rule is deleted.
  10. Click Finish.
Creating an outbound rule