# User cannot authenticate to zoom API on multiple devices

**URL:** <https://devforum.zoom.us/t/user-cannot-authenticate-to-zoom-api-on-multiple-devices/87327>\
**Category:** API and Webhooks\
**Created:** [April 25, 2023, 12:26pm UTC](https://devforum.zoom.us/t/user-cannot-authenticate-to-zoom-api-on-multiple-devices/87327 "2023-04-25T12:26:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![andries](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@andries](https://devforum.zoom.us/u/andries)\
**Post date:** [April 25, 2023, 12:26pm UTC](https://devforum.zoom.us/t/user-cannot-authenticate-to-zoom-api-on-multiple-devices/87327/1 "2023-04-25T12:26:58Z")

</div>

Hi

we have an application that a user can install and use on different devices. Each time the user logs in on another device, the access token on the other devices are invalidated.

So each time a user asks for a refresh token, previous refresh tokens are invalidated.

This causes a lot of troubles…

This has been addresses here, but it seems no solution was provided.

> [@Frequently receiving invalid\_request / token revocation from Zoom](https://devforum.zoom.us/t/frequently-receiving-invalid-request-token-revocation-from-zoom/44220/18):
>
> Understood—thanks Fahad. slight_smile

Main problem is that we can’t even trap this, as we cannot know in advance (when the user clicks on “Authenticate to Zoom”) that the user will try to use the same zoom user.

Kind regards

Andries

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [April 27, 2023, 2:30pm UTC](https://devforum.zoom.us/t/user-cannot-authenticate-to-zoom-api-on-multiple-devices/87327/2 "2023-04-27T14:30:31Z")

</div>

Hi @andries  
Thanks for reaching out to us!  
I understand how this can be causing issues with your integration.  
I have looked for internal documentation and I can see that this feature is in our Roadmap but not implemented yet.

Cheers,  
Elisa

---

<div class="post-metadata">

**Author:** ![andries](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@andries](https://devforum.zoom.us/u/andries)\
**Post date:** [April 27, 2023, 4:10pm UTC](https://devforum.zoom.us/t/user-cannot-authenticate-to-zoom-api-on-multiple-devices/87327/3 "2023-04-27T16:10:00Z")

</div>

problem is that we will be forced in june to switch away from JWT to oAuth… so that is really a problem actually. Or is there a workaround that I don’t see at the moment?

I could centralise the storage of access tokens so that they have to request it from my server, but that looks like a security issue to me…

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [April 27, 2023, 7:56pm UTC](https://devforum.zoom.us/t/user-cannot-authenticate-to-zoom-api-on-multiple-devices/87327/4 "2023-04-27T19:56:34Z")

</div>

@andries  
Have you looked into our Server to SErver OAuth app?  
[https://developers.zoom.us/docs/internal-apps/](https://developers.zoom.us/docs/internal-apps/)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [April 30, 2024, 11:33am UTC](https://devforum.zoom.us/t/user-cannot-authenticate-to-zoom-api-on-multiple-devices/87327/5 "2024-04-30T11:33:09Z")

</div>

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