Invalid Signature when updated to 1.8.0

Meeting SDK Web
1

Description
we have updated the local web SDK sample to latest web sdk 1.8.0 … We are now getting and error as invalid signature

Error
Join meeting timeout
invalid signature

Which version?
earlier 1.7.6 now 1.8.0

App Signature*

Smartphone (please complete the following information):

  • Device: [e.g. pc]
  • OS: [e.g. window 10 ]
  • Version:
  • Browser:[ Chrome]

Additional context
before updating the web sdk to 1.8.0 error was a connection time out.
after updating the web sdk to 1.8.0 error was invalid signature

2

{method: “join”, status: false, result: “Invalid signature.”, errorMessage: “Signature is invalid.”, errorCode: 3712}
erorr log

3

Hey @gangurisatya,

It looks like you’re trying to start a meeting (you’re passing in role 1), but the meeting you’re trying to start isn’t owned by the JWT app owner. In other words, this is your meeting number, but the web SDK credentials you’re passing in the base64 encoded signature actually belong to a different account.

These credentials must belong to the same account the meeting belongs to.

I hope this helps to clarify!

Thanks,
Will

1 Like
4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.