| Status | ||||||
|---|---|---|---|---|---|---|
|
...
Create a Server-to-server OAuth 2.0 app following this article: https://marketplace.zoom.us/docs/guides/build/server-to-server-oauth-app/
| Note |
|---|
A know bug in Zoom APIs invalidates every Server-to-server OAuth tokens upon requesting a new one, so a single OAuth app can ONLY be used by one server. If you plan to use multiple servers, create an app for each of them |
...
. |
- Apply the required granular scopes to the app:
...
Follow the steps below to create a new Verba Import source for Zoom:
Step 1 - Open the Verba Web interface then select Data / Import Sources from the top menu
...
| Name | Description |
|---|---|
| API Key | The Zoom API key associated with the Zoom application registered earlier |
| API Secret | The Zoom API secret associated with your Zoom application registered earlier |
| Forward Proxy Address | IP of the forward proxy server. If left empty, no attempt is made for establishing a forward proxy connection. |
| Forward Proxy Port | Port for the forward proxy connection. |
| Forward Proxy User | Username for authenticating with the Forward Proxy. If left empty, authentication is omitted. |
| Forward Proxy Password | Password for authenticating with the Forward Proxy. |
| API Address | The base URL of the Zoom API |
TLS Certificate File / Thumbprint | Specify the certificate file / certificate thumbprint that is being used for the Zoom API connection. If left empty then the Verba default certificate will be used. |
TLS Key File | Specify the file where the certificate key is stored if not in the windows certificate store. |
TLS Key Password | Specify the password for the file that contains the certificate keys. |
TLS Trust List | Specify the list of certificates that Verba trusts from a 3rd-party connection. Available options:
|
...