Invalid Signature- with 3.1.6 SDK

[nsaxena (Nikhil Saxena)]

After upgrading SDK when launching meeting room getting Invalid Signature, here is detail I am sending, I have changed sdkKey rest detail is correct. Please advise.

{
“sdkKey”: “xxxxxxx”,
“signature”: “eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJyb2xlIjoiMSIsIm1uIjo4MTY5MzQwMDkyNywic2RrS2V5IjoiOFpfT2VXYXRTdzZuZlhvV05RYmFpQSIsInVzZXJOYW1lIjoicUtlZEhJTmtDZ1lnZ0pMb01mTlptMmtwT3ZXYWxhLjEiLCJleHAiOiIxNzA5MzUzMDE5IiwiaWF0IjoiMTcwOTMyNDIxOSIsInRva2VuRXhwIjoiTWFyY2gsIDAxIDIwMjQgMjM6MTY6NTkifQ.Fv0M0S3duJlBSbtvjgDWXTl5ZgkPOMC06Kf5dLWDxvA”,
“exp”: 20000,
“mn”: “81693400927”,
“leaveUrl”: “/ZoomMeeting/end-meeting.cfm”,
“name”: “Nikhil Saxena”,
“pwd”: “redacted”,
“email”: “”,
“role”: “1”,
“zak”: “eyJzdiI6IjAwMDAwMSIsImFsZyI6IkhTNTEyIiwidiI6IjIuMCIsImtpZCI6IjBkOTc5ZjVlLWYyNjctNDk3Zi05NTFjLWI5ZDEwZDU1YmVkZiJ9.eyJhdWQiOiJodHRwczovL29hdXRoLnpvb20udXMiLCJ1aWQiOiJFellRaUtLbFFuQ1E4cjNsaGhCZHd3IiwidmVyIjo5LCJhdWlkIjoiYTU2ZjA4MWIzNzNhYzFlYTNmNmVkN2IyY2I2MzBiODgiLCJuYmYiOjE3MDkzMjQxODMsImNvZGUiOiIyU0k2NkJPTFJyeVZWaXdzRzBCVmRnRGNIMjA5MFBLWEciLCJpc3MiOiJ6bTpjaWQ6OWczYjFNSnRURWVzZWlWMFJrS0hIZyIsImdubyI6MCwiZXhwIjoxNzA5MzI3NzgzLCJ0eXBlIjozLCJpYXQiOjE3MDkzMjQxODMsImFpZCI6InBjVzk3TlNvUl9lQlZwQVBlTm5fUVEifQ.1O9YE6tz4H1Puw5nesSEaPmzQHA92K2kBB-d5MHlH3-5mI6hxqJWqpsrhZmLCWlWcHoC1XQohr8SJPeS5iRKfg”,
“NO_BUTTON_LEAVE”: false,
“NO_TEXT_PASSWORD”: false,
“lang”: “en-US”
}

[chunsiong.zoom (Chun Siong (tag me for response))]

@nsaxena ,

Could you leave out the double quotes for role, iat and exp?

[nsaxena (Nikhil Saxena)]

@chunsiong.zoom , It did not help, kindly advise. Here is my new payload detail without double quotes as you advised, earlier with 2.10.1 SDK it was working but It started problem after upgrading to 3.1.6 SDK

{
“sdkKey”: “xxxxxxx”,
“signature”: “eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJyb2xlIjoiMSIsIm1uIjo4MjYyMjAyODMzOSwic2RrS2V5IjoiOFpfT2VXYXRTdzZuZlhvV05RYmFpQSIsInVzZXJOYW1lIjoiQm9vNmNnV3g1bks5U0RMWnc4TjdFeUlidVJXUWtkLjEiLCJleHAiOiIxNzA5NjAxMTc1IiwiaWF0IjoxNzA5NTcyMzc1LCJ0b2tlbkV4cCI6Ik1hcmNoLCAwNCAyMDI0IDIwOjEyOjU1In0.01rerIGPdgocZyzMz0rlJYpmOau0ZiQsvOV3O8EguDA”,
“exp”: 20000,
“mn”: “82622028339”,
“leaveUrl”: “/ZoomMeeting/end-meeting.cfm”,
“name”: “Nikhil Saxena”,
“pwd”: “redacted”,
“email”: “”,
“role”: 1,
“zak”: “eyJzdiI6IjAwMDAwMSIsImFsZyI6IkhTNTEyIiwidiI6IjIuMCIsImtpZCI6ImMxMTMzYWFhLTQyN2QtNGRmMi1hODFmLWQ4MDRmNjUyNjU2MSJ9.eyJhdWQiOiJodHRwczovL29hdXRoLnpvb20udXMiLCJ1aWQiOiJFellRaUtLbFFuQ1E4cjNsaGhCZHd3IiwidmVyIjo5LCJhdWlkIjoiYTU2ZjA4MWIzNzNhYzFlYTNmNmVkN2IyY2I2MzBiODgiLCJuYmYiOjE3MDk1NzIzMzAsImNvZGUiOiJMei1lTWtZSVIteUZLaVJRbmFtbjNRRHAyMm9qSWk5a1EiLCJpc3MiOiJ6bTpjaWQ6OWczYjFNSnRURWVzZWlWMFJrS0hIZyIsImdubyI6MCwiZXhwIjoxNzA5NTc1OTMwLCJ0eXBlIjozLCJpYXQiOjE3MDk1NzIzMzAsImFpZCI6InBjVzk3TlNvUl9lQlZwQVBlTm5fUVEifQ.cAnM0xZpPqHBxirienHqufytgVtPixuzTsKIgEkp08IrISKbl4PJOiOI6aNBjbA5ntfKmvpPanlSIGVKNbXRMg”,
“NO_BUTTON_LEAVE”: false,
“NO_TEXT_PASSWORD”: false,
“lang”: “en-US”
}

[chunsiong.zoom (Chun Siong (tag me for response))]

@nsaxena
exp is still in quotes,
role is still in quotes,
tokenExp should be the same value as exp

Could you try changing them and let me know if it works?

[nsaxena (Nikhil Saxena)]

@chunsiong.zoom , here is my new payload, appear now all values are same as you advised. Meanwhile I am validating application server time at my end.

Please review attached screenshot,

{
“sdkKey”: “8Z_OeWatSw6nfXoWNQbaiA”,
“signature”: “eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJyb2xlIjoxLCJtbiI6ODg5MDczNTI0ODksInNka0tleSI6IjhaX09lV2F0U3c2bmZYb1dOUWJhaUEiLCJ1c2VyTmFtZSI6IjRzNDVSMXBwdlE2R2JrR0hQanl6ZnVsODRHaE9ici4xIiwiZXhwIjoxNzA5NjI2NTM4LCJpYXQiOjE3MDk2MTk3NTgsInRva2VuRXhwIjoxNzA5NjI2NTM4fQ.py6Z4qDhv8p9md2ku0SrBwwCwzJMHtyZ_CzdRJLVRzY”,
“exp”: 20000,
“mn”: 88907352489,
“leaveUrl”: “/ZoomMeeting/end-meeting.cfm”,
“name”: “Nikhil Saxena”,
“pwd”: “redacted”,
“email”: “nikhil.saxena@abc.com”,
“role”: 1,
“zak”: “eyJzdiI6IjAwMDAwMSIsImFsZyI6IkhTNTEyIiwidiI6IjIuMCIsImtpZCI6IjhlNGQ5YzM5LThjZDgtNDU5Yi04ZTVlLWQ5OWJiN2U0ZjI1YSJ9.eyJhdWQiOiJodHRwczovL29hdXRoLnpvb20udXMiLCJ1aWQiOiJFellRaUtLbFFuQ1E4cjNsaGhCZHd3IiwidmVyIjo5LCJhdWlkIjoiYTU2ZjA4MWIzNzNhYzFlYTNmNmVkN2IyY2I2MzBiODgiLCJuYmYiOjE3MDk2MTkyOTIsImNvZGUiOiJ5M2lpdk9pRFExNm81c3JRaWJ4dVVnRjRSV2pBV2ZPMXkiLCJpc3MiOiJ6bTpjaWQ6OWczYjFNSnRURWVzZWlWMFJrS0hIZyIsImdubyI6MCwiZXhwIjoxNzA5NjIyODkyLCJ0eXBlIjozLCJpYXQiOjE3MDk2MTkyOTIsImFpZCI6InBjVzk3TlNvUl9lQlZwQVBlTm5fUVEifQ.Ygxry_e3H8ydfwf-Z3WJVNRCBrQxXBU5wFn4vFV1UrZJ2Xt-VsbaZtJuCdDvYi8WJRDdYyh1E9I9Ln1ep_YvFA”,
“NO_BUTTON_LEAVE”: false,
“NO_TEXT_PASSWORD”: false,
“lang”: “en-US”
}

screenshot -

[chunsiong.zoom (Chun Siong (tag me for response))]

@nsaxena ,

It seems like this token works

[nsaxena (Nikhil Saxena)]

@chunsiong.zoom , I am getting error “Invalid Signature” and when validating at JSON Web Tokens - jwt.io, you can see above screenshot, it is saying Invalid Signature.

Please advise.

[chunsiong.zoom (Chun Siong (tag me for response))]

@nsaxena for JWT.io you need to input your secret to validate.

I can confirm that your token works, you ac. Try without the Zak token to reduce additional points of failure for now

[nsaxena (Nikhil Saxena)]

@chunsiong.zoom , I agree when I passed with secret key JWT.io showing me validate siguatnure. Below is screenshot.

This time I sent below payload without Zaktoken but no luck and same issue is happening.

Please advise.

{
“sdkKey”: “8Z_OeWatSw6nfXoWNQbaiA”,
“signature”: “eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJyb2xlIjoxLCJtbiI6ODg0MTM4NDY3MjEsInNka0tleSI6IjhaX09lV2F0U3c2bmZYb1dOUWJhaUEiLCJ1c2VyTmFtZSI6IkFCaVZHVnFSSFpvUXBZVlo3Q1JRNWZnanRwWHhPdS4xIiwiZXhwIjoxNzA5NjQyMDM3LCJpYXQiOjE3MDk2MzUyNTcsInRva2VuRXhwIjoxNzA5NjQyMDM3fQ.16Ldr9GLGwanuuOs7T1D-JCT5tzDUYqLhf8ipdX8wyI”,
“exp”: 20000,
“mn”: 88413846721,
“leaveUrl”: “/ZoomMeeting/end-meeting.cfm”,
“name”: “Nikhil Saxena”,
“pwd”: “redacted”,
“email”: “nikhil.saxena@abc.com”,
“role”: 1,
“NO_BUTTON_LEAVE”: false,
“NO_TEXT_PASSWORD”: false,
“lang”: “en-US”
}

[chunsiong.zoom (Chun Siong (tag me for response))]

@nsaxena are you using our sample app btw?

[nsaxena (Nikhil Saxena)]

@chunsiong.zoom , I verified timzone/server time is sync with real time. And we integrated zoom environment within our business application and from there we are calling Zoop APIs to open zoom meeting room.
It was working fine before SDK upgrade.

Please advise.

[chunsiong.zoom (Chun Siong (tag me for response))]

@nsaxena can you try out with this URL?

https://msdk-purejs.asdc.cc/index-manual-jwt-316.html?meetingNumber=&passWord=&role=0&jwt=x.x.x&sdkKey=xxxxxxxxxx&zak=

But fill in the URL with your meetingNumber, passWord, role, JWT Token and sdkKey in the query string

[nsaxena (Nikhil Saxena)]

Hi @chunsiong.zoom , I am having still issue when passing values in URL which you provided me.

can we schedule a meeting so that you can see issue what is happening? Please confirm.

Regards

[chunsiong.zoom (Chun Siong (tag me for response))]

@nsaxena sorry we don’t do calls over support via the forum.

If you need a callback level of service, I would suggest getting a developer support plan.

Is there any specific error you are getting from the url which I’ve shared?

[nsaxena (Nikhil Saxena)]

@chunsiong.zoom , I hit the below URL with required parameter but no luck, below is screenshot, please advise -

https://msdk-purejs.asdc.cc/index-manual-jwt-316.html?meetingNumber=86536796543&passWord=redacted1&role=1&sdkKey=8Z_OeWatSw6nfXoWNQbaiA&zak=eyJzdiI6IjAwMDAwMSIsImFsZyI6IkhTNTEyIiwidiI6IjIuMCIsImtpZCI6IjYwNjhlN2YzLTg0NDAtNDg1NS04ZmM1LWZhMjk2MDdiNTYzMCJ9.eyJhdWQiOiJodHRwczovL29hdXRoLnpvb20udXMiLCJ1aWQiOiJFellRaUtLbFFuQ1E4cjNsaGhCZHd3IiwidmVyIjo5LCJhdWlkIjoiYTU2ZjA4MWIzNzNhYzFlYTNmNmVkN2IyY2I2MzBiODgiLCJuYmYiOjE3MDk3NTgzMDIsImNvZGUiOiJtb0swTmsyZFNtaXJSYUpLQUpDeEJRSWxFV25xNFpMYzQiLCJpc3MiOiJ6bTpjaWQ6OWczYjFNSnRURWVzZWlWMFJrS0hIZyIsImdubyI6MCwiZXhwIjoxNzA5NzYxOTAyLCJ0eXBlIjozLCJpYXQiOjE3MDk3NTgzMDIsImFpZCI6InBjVzk3TlNvUl9lQlZwQVBlTm5fUVEifQ.pZt0q_WPpuNgm2KLw0M_l_qk4kr93iRJroqKKj06eoQFH1wjEgaeUrgrQZCJeQQZlBWKKlhzXMzT0n5Wx1lyFg&jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhdWQiOm51bGwsImlzcyI6InVlWFVrSko3VHNxbnFyZVBIckVnd3ciLCJleHAiOjE5MTQ2ODEzNjAsImlhdCI6MTU5OTE0MzIwOX0.6W2YnekAILXAvwkCvjWlMTaV8MwTGDUBUtL8xc2WRhA

[chunsiong.zoom (Chun Siong (tag me for response))]

@nsaxena could you try without the zak token?

[nsaxena (Nikhil Saxena)]

@chunsiong.zoom , Here is new URL without zak token and attached screenshot, please go through and advise -

https://msdk-purejs.asdc.cc/index-manual-jwt-316.html?meetingNumber=87803673532&passWord=redacted&role=1&sdkKey=8Z_OeWatSw6nfXoWNQbaiA&jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhdWQiOm51bGwsImlzcyI6InVlWFVrSko3VHNxbnFyZVBIckVnd3ciLCJleHAiOjE5MTQ2ODEzNjAsImlhdCI6MTU5OTE0MzIwOX0.6W2YnekAILXAvwkCvjWlMTaV8MwTGDUBUtL8xc2WRhA

[chunsiong.zoom (Chun Siong (tag me for response))]

@nsaxena ,

I realised you are using a totally different format of token in the jwt query string

The signature below should be used as the JWT Token used in the query string

{
“sdkKey”: “8Z_OeWatSw6nfXoWNQbaiA”,
“signature”: “eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJyb2xlIjoxLCJtbiI6ODg0MTM4NDY3MjEsInNka0tleSI6IjhaX09lV2F0U3c2bmZYb1dOUWJhaUEiLCJ1c2VyTmFtZSI6IkFCaVZHVnFSSFpvUXBZVlo3Q1JRNWZnanRwWHhPdS4xIiwiZXhwIjoxNzA5NjQyMDM3LCJpYXQiOjE3MDk2MzUyNTcsInRva2VuRXhwIjoxNzA5NjQyMDM3fQ.16Ldr9GLGwanuuOs7T1D-JCT5tzDUYqLhf8ipdX8wyI”,
“exp”: 20000,
“mn”: 88413846721,
“leaveUrl”: “/ZoomMeeting/end-meeting.cfm”,
“name”: “Nikhil Saxena”,
“pwd”: “redacted”,
“email”: “nikhil.saxena@abc.com”,
“role”: 1,
“NO_BUTTON_LEAVE”: false,
“NO_TEXT_PASSWORD”: false,
“lang”: “en-US”
}

[nsaxena (Nikhil Saxena)]

@chunsiong.zoom , It is not helping when replaced current signature with zaktoken. I need working session with you. or advise.
We have business plan. Please provide contact person or email where I connect…

[chunsiong.zoom (Chun Siong (tag me for response))]

@nsaxena the issue you are facing is caused by using the wrong token.

I would recommend checking out the guide here on how to generate the SDK auth token

Meeting SDK Auth

If you would like to have dedicated support, I would recommend you to signing up for a developer support plan.

Here’s the issue.

1. Your SDK signature(aka JWT Token) is not correct. You cannot use your ZAK token here.

This SDK Auth token which you have previously shared already works

eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJyb2xlIjoxLCJtbiI6ODg0MTM4NDY3MjEsInNka0tleSI6IjhaX09lV2F0U3c2bmZYb1dOUWJhaUEiLCJ1c2VyTmFtZSI6IkFCaVZHVnFSSFpvUXBZVlo3Q1JRNWZnanRwWHhPdS4xIiwiZXhwIjoxNzA5NjQyMDM3LCJpYXQiOjE3MDk2MzUyNTcsInRva2VuRXhwIjoxNzA5NjQyMDM3fQ.16Ldr9GLGwanuuOs7T1D-JCT5tzDUYqLhf8ipdX8wyI

But subsequently you shared another SDK auth token which is of a totally different format, hence the issue you are facing.

eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhdWQiOm51bGwsImlzcyI6InVlWFVrSko3VHNxbnFyZVBIckVnd3ciLCJleHAiOjE5MTQ2ODEzNjAsImlhdCI6MTU5OTE0MzIwOX0.6W2YnekAILXAvwkCvjWlMTaV8MwTGDUBUtL8xc2WRhA

2. Do not use any ZAK token during this troubleshooting period. We do not need the ZAK token right now

3. You can see for format of the token using https://jwt.io to decode the auth signature