New connection invalidates all refresh tokens

Meeting SDK
1

Our developers integrate the zoom meeting API on their local computers. If they connect the test account (let’s say dev@zoom), the integration works.
If we release the code to our staging environment, and connect the test account (again dev@zoom) there, all local integrations do not work anymore, because all refresh_tokens are invalidated.

Does zoom only allow one connection between user and app? How can we prevent this?

We have an app, where users have multiple accounts (multi tenant) (need to be separated because of tax reasons), but they connect zoom with the same zoom account. So this would always invalidate the other connected account in our app.

1 Like
2

Hi ,
I believe the reason this is happening is because if the user logs into your app from various devices, Zoom invalidates the previous refresh_token and as such they will not work.
You may have to create a separate app for your local and staging environment, to avoid this.

2 Likes
3

I think so too, but why? Any other provider has something where you can see your connections and can disconnect them if needed.

4

Hi @Fario_Consulting , thank you for sharing and helping @blablubbbla . I recommend making a Feature Requests for that ability.

5

I created a new Feature Request