Also you must have at least a Pro Zoom account to use the SDK which could be the reason you are seeing that error. If you would like a free trial for development / testing purposes we can request that for you.
I am also experiencing this issue. Created a JWT App with key. Now what am I suppose to do with WebSDK? As of now I was generating signature and then passing it into init phase.
I can’t find any related (valid) documentation of steps necessary to join webinar with JWT access token.
Went through API docs, but can’t find related endpoint to which I should send my webinar ID and other params to obtain signature necessary for joining.
Thanks for help!
Thanks for quick reply. I do know all the other params necessary for joining webinars. I did use API keys for development, but once deployed on production stack, I am having an issue with webinar joining bcs of the signature. So my question is - how to generate signature when using JWT?
My join code looks like this
signature: ???signature???, // how to calculate it when using JWT?
Yes, we were generating signature but the generated token is not working when passed into join method. It returns errorCode 1 - join failed.
When generating locally (using ZoomMtg.generateSignature) - joining works fine.
I am struggling getting to know differences between SDK API keys vs JWT.
Anyhow currently we have sample code for generating signature at our API and when trying to join webinar, we are failing with generic error (but the only thing that changes is signature, so I assume the reason behind this issue lies somewhere near).
Can you please be more specific when we must use JWT (and how to use it) and when we can use generating signature from sample code?
have our custom API zoom/signature that returns signature based on your sample code.
once using this signature, I can’t join the webinar with generic error message
We use real meeting ID (9 digits, no dashes)
As we were debugging this - WebSDK generateSignature returns slightly different signatures than your Node.js sample code. We put there the same timestamp, same meeting ID, same email and username with different signature results.