# WebSDK Signature

**URL:** <https://devforum.zoom.us/t/websdk-signature/85540>\
**Category:** Web\
**Created:** [March 28, 2023, 10:00pm UTC](https://devforum.zoom.us/t/websdk-signature/85540 "2023-03-28T22:00:57Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [April 4, 2023, 6:34am UTC](https://devforum.zoom.us/t/websdk-signature/85540/6 "2023-04-04T06:34:27Z")

</div>

@nhendry,

@j.schoenemeyer is correct, you should not create the signature on the client browser. Instead, it should be generated on the backend. Here is a helpful developer forum post that you can refer to for troubleshooting SDK JWT:

> [@Troubleshooting Meeting SDK signature validation](https://devforum.zoom.us/t/troubleshooting-meeting-sdk-signature-validation/85961):
>
> In this guide, we’ll cover common issues you may run into when generating a signature for the Zoom Meeting SDK. The Zoom Meeting SDK uses a JSON Web Token (JWT) signature to authorize the SDK and validate your client’s requests to start or join a meeting. Documentation on this is available here: [Meeting SDK Authorization](https://developers.zoom.us/docs/meeting-sdk/auth/). We also have a sample signature application which can be used as a good starting point: [Sample Meeting SDK Signature App - Node JS](https://github.com/zoom/meetingsdk-sample-signature-node.js) If the signature provided is invalid, the…

---

_[View the full topic](https://devforum.zoom.us/t/websdk-signature/85540)._
