Duaer

Integrations

Set up Zoom credentials in Duaer

Store Zoom connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.

Create a Zoom OAuth app

Zoom no longer supports JWT apps, so the Duaer Zoom API (JWT Token) credential no longer works. Use Zoom OAuth2 API instead:

  1. In the Zoom App Marketplace, click Develop > Build App and choose General App, authorized by users.
  2. In the app’s OAuth settings, set both Redirect URL and OAuth Allow List to the Duaer OAuth Redirect URL.
  3. Under Scopes, add the meeting scopes the node needs, such as meeting read and write.
  4. Put Client ID and Client Secret in the Duaer credential and click Connect my account.

A Zoom Server-to-Server OAuth app does not fit this credential. It needs a General App that a user authorizes in the browser.

Zoom API

In Duaer, choose Zoom API when you create a credential, then fill in these fields:

  • JWT Token (secret)

Note from the dialog: On 1 June, 2023 Zoom will remove JWT App support. You will have to connect to Zoom using the Oauth2 auth method. More details (zoom.us) (https://developers.zoom.us/docs/integrations/oauth/)

When you save, Duaer tests the connection with these values.

Duaer nodes that use it: Zoom.

Zoom OAuth2 API

In Duaer, choose Zoom OAuth2 API when you create a credential, then fill in these fields:

  • Client ID (required)
  • Client Secret (required, secret)

Duaer uses the OAuth2 Authorization Code grant for this type.

In the provider’s app settings, register the OAuth Redirect URL that the Duaer credential dialog shows (https://<your-duaer-host>/rest/oauth2-credential/callback). Then click Connect my account in Duaer and approve access.

Optional settings shared by every Duaer OAuth2 credential: Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under OAuth2 API.

Duaer nodes that use it: Zoom.

Zoom Server-to-Server OAuth API

In Duaer, choose Zoom Server-to-Server OAuth API when you create a credential, then fill in these fields:

  • Account ID (required)
  • Client ID (required)
  • Client Secret (required, secret)

When you save, Duaer tests the connection with these values.

Save the connection in Duaer

Open Credentials and create Zoom. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.

Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys. The matching node is under the related node.

Who can use this credential

Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.

Questions

Do Zoom secret values appear in Duaer node parameters?

No. In Duaer, Zoom secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

What usually stops a Zoom credential from saving in Duaer?

Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields Zoom expects, then confirm you can create credentials in that project.

In this section