# Granting more than 1 refresh token per user / client ID

**URL:** <https://devforum.zoom.us/t/granting-more-than-1-refresh-token-per-user-client-id/13560>\
**Category:** API and Webhooks\
**Created:** [April 16, 2020, 6:52pm UTC](https://devforum.zoom.us/t/granting-more-than-1-refresh-token-per-user-client-id/13560 "2020-04-16T18:52:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jared\_Morse](https://avatars.discourse-cdn.com/v4/letter/j/57b2e6/32.png) [@Jared\_Morse](https://devforum.zoom.us/u/Jared_Morse)\
**Post date:** [April 16, 2020, 6:52pm UTC](https://devforum.zoom.us/t/granting-more-than-1-refresh-token-per-user-client-id/13560/1 "2020-04-16T18:52:30Z")

</div>

**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 granted tokens from Zoom for the same user / client ID. Creating a second client ID (aka marketplace app) isn’t desirable.

**Error**  
Previous access/refresh tokens are immediately expired.

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

**Which Endpoint/s?**  
Any

**How To Reproduce (If applicable)**  
Steps to reproduce the behavior:

1. Grant an access/refresh token to a user for a given client ID.
2. Grant another access/refresh token to the same user and client ID.
3. access/refresh token from 1 no longer work.

**Screenshots (If applicable)**  
n/a

**Additional context**  
n/a

---

<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:** [April 17, 2020, 9:09pm UTC](https://devforum.zoom.us/t/granting-more-than-1-refresh-token-per-user-client-id/13560/2 "2020-04-17T21:09:48Z")

</div>

Hey @Jared_Morse,

Please see my post here:

> [@OAuth Access & refresh token questions](https://devforum.zoom.us/t/oauth-access-refresh-token-questions/13617/2):
>
> Hey @hunter.steele2, Yes, the webhooks will still send! Refreshing your token on demand is the suggested flow so you are good! slight_smile Hey @hunter.steele2, Yes, if a user logins in on a different device, the OAuth flow basically restarts, invalidating the current OAuth access and refresh tokens you have stored. You will need to get the access\_token again upon new authorization and update your save tokens with the new tokens. Thanks, Tommy

We are working to support multiple tokens for OAuth in the future.

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![Jared\_Morse](https://avatars.discourse-cdn.com/v4/letter/j/57b2e6/32.png) [@Jared\_Morse](https://devforum.zoom.us/u/Jared_Morse)\
**Post date:** [April 17, 2020, 10:04pm UTC](https://devforum.zoom.us/t/granting-more-than-1-refresh-token-per-user-client-id/13560/3 "2020-04-17T22:04:44Z")

</div>

Thanks Tommy, glad to hear it. I realize it’s hard to give an ETA, but do you think this is a next month thing or a next year thing?

---

<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:** [April 19, 2020, 6:28am UTC](https://devforum.zoom.us/t/granting-more-than-1-refresh-token-per-user-client-id/13560/4 "2020-04-19T06:28:41Z")

</div>

Hey @Jared_Morse,

Most likely next year.

Thanks,  
Tommy

---

<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, 8:32pm UTC](https://devforum.zoom.us/t/granting-more-than-1-refresh-token-per-user-client-id/13560/5 "2020-08-21T20:32:51Z")

</div>

Closed on August 21, 2020, 8:32pm UTC


