Issues with Zoom SDK and REST API Using Server-to-Server and General App Credentials

Meeting SDK
,
1

Hi Everyone ,

I am reaching out to seek assistance regarding an issue I have encountered while working with Zoom’s Server-to-Server OAuth and General App credentials(OAuth 2.0).

I am using “@zoom/meetingsdk”: “3.6.0”, meeting sdk .

Previously, I was using the Server-to-Server OAuth app in the Zoom Marketplace. While this allowed me to create and manage meetings using the Zoom REST APIs without any issues, I encountered a problem when attempting to join a meeting via the Zoom Meeting SDK. Specifically, I kept receiving an error stating that the signature is invalid when generating the token(signature) for the Meeting SDK.

In an attempt to bypass this problem, I switched to using General App credentials. With these credentials, I am now able to join the meeting using the Meeting SDK without any issues. However, I am facing a new challenge when trying to create an authorization code for accessing the REST APIs. The General App credentials workflow requires me to navigate to a page where I must manually allow permissions. Without doing so, I am unable to generate the authorization code and, consequently, cannot obtain the access token needed to manage meetings through the REST APIs.

Given my requirements, I need a solution that allows me to:

  1. Join meetings using the Zoom Meeting SDK without facing the “signature is invalid” issue.
    Manage meetings (create, update, delete) programmatically using the Zoom REST APIs without needing user interaction to grant permissions each time.
  2. Could you please advise on the best course of action to achieve both functionalities—using the Meeting SDK to join meetings and managing meetings through the REST APIs—without manual intervention?
  3. Can we use server-to-server OAuth credentials to join the meeting using meeting SDK

Thank you all for your time and support. I look forward to your responses.

2

@vikasbansal.se
If you wish to generate a signature for Meeting SDK, you will either need a Meeting SDK App (deprecated) or General App. This is not a workaround/bypass. It has has been always the case.

In an attempt to bypass this problem, I switched to using General App credentials. With these credentials, I am now able to join the meeting using the Meeting SDK without any issues. However, I am facing a new challenge when trying to create an authorization code for accessing the REST APIs. The General App credentials workflow requires me to navigate to a page where I must manually allow permissions. Without doing so, I am unable to generate the authorization code and, consequently, cannot obtain the access token needed to manage meetings through the REST APIs.

The General App uses user level OAuth flow. You will need Server to Server OAuth app to get admin level access for REST API.

In other works, you will need both General App and Server to Server App.