# Browser signature authentication using Uppy + Transloadit

**URL:** <https://community.transloadit.com/t/browser-signature-authentication-using-uppy-transloadit/15904>\
**Category:** Uppy\
**Created:** [November 29, 2021, 7:55pm UTC](https://community.transloadit.com/t/browser-signature-authentication-using-uppy-transloadit/15904 "2021-11-29T19:55:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Murdock](https://avatars.discourse-cdn.com/v4/letter/m/2bfe46/32.png) [@Murdock](https://community.transloadit.com/u/Murdock)\
**Post date:** [November 29, 2021, 7:55pm UTC](https://community.transloadit.com/t/browser-signature-authentication-using-uppy-transloadit/15904/1 "2021-11-29T19:55:43Z")

</div>

We’re looking into Uppy integration, and I can’t find clear documentation on how to ping our back-end for signature generation from a browser front-end. We need to restrict uploads to logged-in users, so prior to initiating upload we need to hit our back-end, verify the user is logged in, then generate the transloadit signature for signature Authentication.

Can someone point me at an example of this flow? I assume it’s a common one. Or, if I have this wrong, could you suggest the best way for us to incorporate login verification prior to Uppy\>Transload\>S3 flow?

Thanks!