# Multiple refresh tokens ETA?

**URL:** <https://devforum.zoom.us/t/multiple-refresh-tokens-eta/50310>\
**Category:** Feature Requests\
**Created:** [May 15, 2021, 4:21am UTC](https://devforum.zoom.us/t/multiple-refresh-tokens-eta/50310 "2021-05-15T04:21:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ethan4](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ethan4/32/27142_2.png) [@ethan4](https://devforum.zoom.us/u/ethan4)\
**Post date:** [May 15, 2021, 4:21am UTC](https://devforum.zoom.us/t/multiple-refresh-tokens-eta/50310/1 "2021-05-15T04:21:16Z")

</div>

**Description**  
Trying to grant a second OAuth token expires the first one. We have two separate apps/databases but from the user’s perspective they are the same software. Raising the limit to a few more would help us tremendously. Some old threads seemed to indicate support for this was coming sometime this year. Is this still on the roadmap, and is there an ETA? Thanks.

**Which App Type (OAuth / Chatbot / JWT / Webhook)?**  
OAuth

**Additional context**  
Previous threads below indicating that ETA might be this year

> [@Granting more than 1 refresh token per user / client ID](https://devforum.zoom.us/t/granting-more-than-1-refresh-token-per-user-client-id/13560):
>
> Description Trying to grant a second refresh token to a user (on the same client ID) expires the first one. This is somewhat unexpected given that most OAuth2 implementations allow more than one. I realize this might be considered “working as intended”, but it’s very restrictive. Even bumping the limit to 5-10 would help. The use-case here is that we run two separate apps/databases that are technically the same piece of software (from a customer POV), so we want both apps to be able to be g…

> [@OAuth Tokens invalidated after login with same account elsewhere?](https://devforum.zoom.us/t/oauth-tokens-invalidated-after-login-with-same-account-elsewhere/8640):
>
> 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 toke…

---

<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:** [June 14, 2021, 2:22pm UTC](https://devforum.zoom.us/t/multiple-refresh-tokens-eta/50310/2 "2021-06-14T14:22:08Z")

</div>

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