We’ve discovered a bug with the Web Client SDK where if the meeting passcode starts with a 0, the signature will be invalid, and the ZoomMtg.join() function will throw an error, stating ‘No Permission’.
Unfortunately we discovered this while we were running a live event on our custom-made event platform, however the issue was quickly solved by simply changing the passcode to start with another number.
Please note that the meeting passcode was being passed as a string and included the 0 at the beginning, it was not being trimmed to integer format.
Please let us know when this has been fixed. Until then we are having to manually check all of the meeting passwords when they are generated by the customer.