# Support for multiple refresh tokens for single OAuth application

**URL:** <https://devforum.zoom.us/t/support-for-multiple-refresh-tokens-for-single-oauth-application/56684>\
**Category:** Feature Requests\
**Created:** [August 31, 2021, 6:26am UTC](https://devforum.zoom.us/t/support-for-multiple-refresh-tokens-for-single-oauth-application/56684 "2021-08-31T06:26:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![vedarth](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vedarth/32/21320_2.png) [@vedarth](https://devforum.zoom.us/u/vedarth)\
**Post date:** [August 31, 2021, 6:26am UTC](https://devforum.zoom.us/t/support-for-multiple-refresh-tokens-for-single-oauth-application/56684/1 "2021-08-31T06:26:00Z")

</div>

**Is your feature request related to a problem? Please describe.**  
We want to create more than one refresh/access token for a given user and a given OAuth application, right now if we try to create a new refresh token, the previously created token is invalidated. This problem was reported last year ([Granting more than 1 refresh token per user / client ID - #4 by tommy](https://devforum.zoom.us/t/granting-more-than-1-refresh-token-per-user-client-id/13560/4)) and the last comment was in April of 2020 that this might be implemented next year i.e 2021. So, I wanted to know if there is any update with respect to this problem.

**Describe the solution you’d like**  
We should be able to create more than one refresh tokens for a given user and given OAuth application.