# OAuth Tokens invalidated after login with same account elsewhere?

**URL:** <https://devforum.zoom.us/t/oauth-tokens-invalidated-after-login-with-same-account-elsewhere/8640>\
**Category:** API and Webhooks\
**Created:** [March 13, 2020, 8:58pm UTC](https://devforum.zoom.us/t/oauth-tokens-invalidated-after-login-with-same-account-elsewhere/8640 "2020-03-13T20:58:15Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Randolpho](https://avatars.discourse-cdn.com/v4/letter/r/d9b06d/32.png) [@Randolpho](https://devforum.zoom.us/u/Randolpho)\
**Post date:** [March 13, 2020, 8:58pm UTC](https://devforum.zoom.us/t/oauth-tokens-invalidated-after-login-with-same-account-elsewhere/8640/1 "2020-03-13T20:58:15Z")

</div>

My app is currently using OAuth at a user account level to access the Zoom API.

I have run into an interesting issue and would love some insight.

The OAuth works great, however, I have noticed occasionally that request will return 401 unexpectedly and before its expire time. After investigating, it appears that the token has been invalidated.

I created a couple environments for testing of my app, and I have noticed that if I get a token for the user account in one environment, then get a token for the same user account in another environment, then return to the first environment and try to use the API, I get a 401 error, because the old token is no longer good.

Heck, the issue occurs if I do this in the same environment with two different browsers.

It seems counterintuitive to me that only one token set can be used at a time, and this is intended as a user-level token to enable the user to manage their meetings from our portal.

Did I set up the app wrongly in the marketplace? Or is there a hard line in the sand that only one token can ever be active at a time and thus I’m going to have to re-think how I handle managing a user’s zoom data?

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [March 13, 2020, 10:18pm UTC](https://devforum.zoom.us/t/oauth-tokens-invalidated-after-login-with-same-account-elsewhere/8640/2 "2020-03-13T22:18:44Z")

</div>

Hey @Randolpho,

Currently we don’t support multiple tokens for OAuth, however, we are in the process of developing this.

(ZOOM-88936). Stay updated here: [https://marketplace.zoom.us/docs/changelog](https://marketplace.zoom.us/docs/changelog)

Thanks for you patience,  
Tommy

---

<div class="post-metadata">

**Author:** ![Randolpho](https://avatars.discourse-cdn.com/v4/letter/r/d9b06d/32.png) [@Randolpho](https://devforum.zoom.us/u/Randolpho)\
**Post date:** [March 16, 2020, 12:35pm UTC](https://devforum.zoom.us/t/oauth-tokens-invalidated-after-login-with-same-account-elsewhere/8640/3 "2020-03-16T12:35:21Z")

</div>

Well that’s disappointing, but I can work around it.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [March 16, 2020, 4:52pm UTC](https://devforum.zoom.us/t/oauth-tokens-invalidated-after-login-with-same-account-elsewhere/8640/4 "2020-03-16T16:52:38Z")

</div>

Yes, please implement a work around until we support it.

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![felix](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/felix/32/7500_2.png) [@felix](https://devforum.zoom.us/u/felix)\
**Post date:** [May 2, 2020, 8:08pm UTC](https://devforum.zoom.us/t/oauth-tokens-invalidated-after-login-with-same-account-elsewhere/8640/5 "2020-05-02T20:08:18Z")

</div>

Hi @tommy,

I had the same question as @Randolpho and found this thread. For us, it is a bit harder to work around.

Do you know if this feature / bug is to be addressed soon?

Also, you mention “ZOOM-88936”, what looks like a feature / bug code in your response. Is this surfaced anywhere that I can see?

I followed the link to the Zoom changelog, but I don’t see any codes or any way to search or get alerted.

Best,  
Felix

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [May 6, 2020, 12:09am UTC](https://devforum.zoom.us/t/oauth-tokens-invalidated-after-login-with-same-account-elsewhere/8640/6 "2020-05-06T00:09:55Z")

</div>

Hey @felix,

We have this on our roadmap to implement.

> [@felix](#):
>
> Also, you mention “ZOOM-88936”, what looks like a feature / bug code in your response. Is this surfaced anywhere that I can see?

This is for internal tracking 🙂

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![felix](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/felix/32/7500_2.png) [@felix](https://devforum.zoom.us/u/felix)\
**Post date:** [May 6, 2020, 12:25am UTC](https://devforum.zoom.us/t/oauth-tokens-invalidated-after-login-with-same-account-elsewhere/8640/7 "2020-05-06T00:25:41Z")

</div>

Thanks for the response! I built a workaround.

Best regards.

---

<div class="post-metadata">

**Author:** ![michael.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael.zoom/32/37213_2.png) [@michael.zoom](https://devforum.zoom.us/u/michael.zoom)\
**Post date:** [May 8, 2020, 9:47pm UTC](https://devforum.zoom.us/t/oauth-tokens-invalidated-after-login-with-same-account-elsewhere/8640/8 "2020-05-08T21:47:05Z")

</div>

Great, glad to hear it works currently @felix - let us know if there’s anything we can help with in the mean time.

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 9:07pm UTC](https://devforum.zoom.us/t/oauth-tokens-invalidated-after-login-with-same-account-elsewhere/8640/9 "2020-08-21T21:07:36Z")

</div>

Closed on August 21, 2020, 9:07pm UTC


