# Login again with OAuth

**URL:** <https://devforum.zoom.us/t/login-again-with-oauth/16990>\
**Category:** API and Webhooks\
**Created:** [May 10, 2020, 4:03pm UTC](https://devforum.zoom.us/t/login-again-with-oauth/16990 "2020-05-10T16:03:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ankochem](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ankochem/32/2524_2.png) [@ankochem](https://devforum.zoom.us/u/ankochem)\
**Post date:** [May 10, 2020, 4:03pm UTC](https://devforum.zoom.us/t/login-again-with-oauth/16990/1 "2020-05-10T16:03:50Z")

</div>

**Description**  
Hello, I have a next problem.  
I’m developing app where I do not want to persist any data about the user.  
So, my case is next:

1. User comes to my app
2. User authorizes through Zoom OAuth
3. My app now get access\_token and refresh\_token, and store it, for example, in memory
4. During user session, I use this tokens for using Zoom API.
5. After session expires and user is gone, I drop his access\_token and refresh\_token.  
…  
After a while user come back again and tries to authorize through Zoom OAuth. As far as I understand, now he can’t get new token without old refresh\_token ? So, to use my app again he had to reinstall it, right?  
Am I right, and Are there any workarounds ?

Another question  
Even if I persist tokens for users, what can I do when user is trying to login again through Zoom, or trying to login from another device?  
In this case, My app only will get ‘code’, and will not able to get access\_token with this code (because tokens was already created before).  
But my app can not detect user by code, so my stored tokens are useless.

Thanks a lot for your answers

Thanks a lot for your answer

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

---

<div class="post-metadata">

**Author:** ![samly](https://avatars.discourse-cdn.com/v4/letter/s/a87d85/32.png) [@samly](https://devforum.zoom.us/u/samly)\
**Post date:** [May 10, 2020, 9:53pm UTC](https://devforum.zoom.us/t/login-again-with-oauth/16990/2 "2020-05-10T21:53:29Z")

</div>

You can always regenerate the access\_token by going through the full Authorization process again to “install” the app, even if it’s already installed. You don’t need a refresh\_token to trigger Authorization.

This is a common use-case for OAuth where you do not want to store any user tokens.

---

<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 13, 2020, 11:00pm UTC](https://devforum.zoom.us/t/login-again-with-oauth/16990/3 "2020-05-13T23:00:33Z")

</div>

Hey @ankochem,

Like @samly said, currently Zoom OAuth only supports one set of access / refresh tokens at a time, so in order to use Zoom OAuth through a different device, just [take your users to the authorize url](https://marketplace.zoom.us/docs/guides/auth/oauth#getting-access-token) again, and save the latest tokens if you would like to store them.

Let us know if you have additional questions.

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, 9:18pm UTC](https://devforum.zoom.us/t/login-again-with-oauth/16990/4 "2020-08-21T21:18:43Z")

</div>