# Assigning temporary credentials for remote access to equipment

**URL:** <https://accelerated-discovery.org/t/assigning-temporary-credentials-for-remote-access-to-equipment/241>\
**Category:** Tools\
**Created:** [July 6, 2024, 2:03pm UTC](https://accelerated-discovery.org/t/assigning-temporary-credentials-for-remote-access-to-equipment/241 "2024-07-06T14:03:08Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![sgbaird](https://yyz1.discourse-cdn.com/flex003/user_avatar/accelerated-discovery.org/sgbaird/32/341_2.png) [@sgbaird](https://accelerated-discovery.org/u/sgbaird)\
**Post date:** [July 27, 2024, 1:10am UTC](https://accelerated-discovery.org/t/assigning-temporary-credentials-for-remote-access-to-equipment/241/4 "2024-07-27T01:10:31Z")

</div>

This was very helpful, thanks! At least for a first pass, I will try the JWT tokens issued by [Auth0](https://auth0.com/) and passed to a HiveMQ “Starter Plan” broker. Still figuring out the details, such as the web app for requesting a token (perhaps [a Streamlit Web App in Hugging Face Spaces](https://huggingface.co/spaces/AccelerationConsortium/digital-pipette) [[2](https://chatgpt.com/share/131b6bdf-373e-4b85-83ae-212ce368e42c)] or a [Flask App in PythonAnywhere](https://help.pythonanywhere.com/pages/Flask/)), since it seems like I can’t host that natively in Auth0.

See also a somewhat lengthy [ChatGPT transcript](https://chatgpt.com/share/641f3f73-3fa7-431d-b2c1-dbcc43b1bab3).

Aside: By switching to JWT for the broker, it disables the typical username/password authentication I’ve been used to with HiveMQ.

cc @kenzo

EDIT: [abandoning this approach in favor of something simpler](https://accelerated-discovery.org/t/implementing-jwt-authentication-with-a-hivemq-cloud-broker-starter-plan-for-remote-equipment-access/256/3)

---

_[View the full topic](https://accelerated-discovery.org/t/assigning-temporary-credentials-for-remote-access-to-equipment/241)._