Integrating SailPoint with Zoom

This guide is designed to give specific information about the requirements and field definitions needed to get a working instance of a Zoom source in SailPoint that supports version 2.0 of the Zoom API.

Supported Features

SailPoint's Zoom source supports the following features:

Account Management

• Entitlement Aggregation
• *Password management (Change Password)

• Update of the following attributes:

  • first_name (Maximum 64 characters and cannot contain more than 5 Chinese characters)
  • last_name (Maximum 64 characters and cannot contain more than 5 Chinese characters)
  • dept
  • email (Maximum 128 characters)

  • type: (1, 2, 3)

    The integer value user types are as follows:

    1: Basic

    2: Licensed

    3: On-Prem

    Note

    For any other user type, the valid value is the corresponding integer assigned by Zoom API.

• Load and *provision Zoom Accounts (Enable/Disable)

• *Access Certifications (certification of entitlements connected to accounts)
• Delete Accounts

For more information on features, refer to Source Features.

The Zoom source supports the following Zoom objects:

• Zoom Users as SailPoint Users
• Zoom Web Groups: This is an entitlement object that can be assigned to and removed from, a user of a web group.

Password Management

If Password Management is enabled for your organization, you can change the password for a user of the source. After enabling password management on the source, be aware of the following:

• The password policy defined in SailPoint applies to accounts on this source.
• If you change the password for an application connected to this source, the change will automatically be made to the source itself.

For more information on configuring password management, refer to Password Management Overview.

Supported Managed Systems

The Zoom connector supports Zoom API version 2.0.

Prerequisites

• Configure at least one virtual appliance cluster and successfully test the connection. For instructions, refer to the Virtual Appliance Reference Guide.

• SailPoint's Zoom connector uses rotating refresh tokens authentication from Zoom. After first use of the refresh token for a test connection with the connector, you must save the new refresh token. When creating a refresh token ensure all scopes levels are present for operations like create, remove, group, and user. For more information, refer to OAuth with Zoom.

Required Permissions

Zoom is introducing Classic and granular scopes to allow users to be more specific about the level of access granted to third-party apps. For more information on scopes, refer to OAuth Scopes.

Classic Scopes

Classic scopes provide a way to limit the amount of access granted to an app. Zoom has user-level, admin-level, and Master-level scopes. Previously-created apps use the previously-available scopes, now called classic scopes. If you upgrade your app you will still be able to use classic scopes.

The following scopes are required for aggregation, provisioning, and deprovisioning:

• user:read:admin
• user:write:admin
• account:read:admin
• account:write:admin
• group:read:admin
• group:write:admin
• meeting:read:admin
• meeting:write:admin

The minimum requirements for scopes and their connector operations are as follows:

Granular Scopes

Granular scopes enable developers to practice the principle of least privilege so that users can provide access to the minimal amount of information required by your app. Newly created apps use granular scopes, including new apps created using the new build flow. New apps can also set which scopes are required and which are optional.

The following scopes are required for aggregation, provisioning, and deprovisioning:

• user:read:list_users:admin
• user:read:user:admin
• group:read:list_groups:admin
• user:update:status:admin
• user:write:user:admin
• group:write:member:admin
• group:delete:member:admin
• user:update:password:admin
• user:update:user:admin

The requirements for scopes and their connector operations are as follows:

Upgrade Considerations

• The Zoom connector no longer supports the API Token Authentication. SailPoint recommends you upgrade the applications to use OAuth 2.0 Authentication.

  Note

  You must manually configure your application to use OAuth 2.0 Authentication.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.