Can Server-to-Server OAuth credentials be used for Meeting SDK (Web) signature signing?

Meeting SDK Web
1

Hello,

We have a Server-to-Server OAuth app set up and working - we’re successfully using it to call the REST API (e.g. listing users).

We now want to embed meetings with the Meeting SDK for Web, which requires generating a signature.

My question: Can we use the same credentials (our existing Server-to-Server OAuth app’s Client ID / Client Secret) to sign the Meeting SDK signature? Or, can we create a Web SDK app and then use the credentials for that to call the APIs? Or are 2 apps required?

Thank you

2

@tcsteve you can use 1 General app to generate the signature and call APIs.

If there are specific scopes which are only available in S2S, then will need 2 apps.

3

Thank you @chunsiong.zoom

Is it possible to enable the Meeting SDK on a S2S app, so that we can use the S2S client ID and client secret for the Meeting SDK? I think the answer is no, but just trying to verify that.

Part of our use-case is to avoid any interactive authentication with Zoom for our end users, so we’re looking for a way for the admins setting up our platform to enter the Zoom API keys and secrets and IDs once, and then their end users don’t need to further authenticate with Zoom in our platform. We could do all of this years ago with the JWT apps, but it sounds like that functionality was split into two different places.

The things we’re using the S2S app for now include listing the Zoom users on the account, fetching users ZAK tokens, and creating meetings for Zoom users. Then we use the meeting SDK in component view to launch the meeting for the host and other participants.

Thanks for your clarification.

4

@tcsteve you cannot use s2s for meeting sdk signature generation. You need to you a general app with meeting sdk enabled in the embed tab