Invalid signature error 3712

Meeting SDK
1

I have a General App that I use to embed a client in a webpage. It’s still in draft mode and I use the development keys. That is able to join meetings created by an S2S app managed by the same account.

However, I wanted this app to be under a generic “services@…” account and not under my name.

So I then created another General App under the services@ email address. I also created another S2S under the services@ email address

With the same code, but using the development keys of the new app, I get an “invalid signature” error when trying to join meetings created by the new S2S app. I’m kind of stuck on how to debug. It’s the same code just different auth info. I also used jwt.io to ensure the payload is correct and also I validated the secret.

It’s not a code issue it’s some configuration issue but both General Apps have the same permissions. The only difference is that the new S2S app has more permissions than the first S2S app.

Any guidance is appreciated

2

Hello, there are already similar topics on the forum that are marked as resolved. Please try checking them.

In addition, based on your description, you can check the following:

  1. Whether Meeting SDK is enabled in your General App.

    image
    image1317×382 42.9 KB

  2. The Zoom account that is hosting the conference must be the account from which the Zoom General App is created (or added to it via “User Management” if using Zoom Workplace Pro).

1 Like
3

#1 and #2 are true. I wasn’t able to find my answer, but miraculously that problem went away.

I had another issue and that was the Zoom General App was embedded and loading properly on localhost. However when running it on a legitimate https enabled URL I would get an error stating the same thing–invalid signature

That also, without any code change on my part, started to work.

Is there perhaps a large delay in Zoom backend services after registering and so forth?

4

Hey @Christopher3
Happy to hear the issue went away, I am not sure what could have been the issue.
Feel free to create a new topic if this happens again and tag me

@dmitryukhanov thanks a LOT for your help