OAuth refresh token process change? Was working, now not

The token refresh process, working a couple weeks ago, seems to not work now.


401 - Unauthorized
“{“reason”:“Invalid Token!”,“error”:“invalid_request”}”

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

Which Endpoint/s?

How To Reproduce (If applicable)
May not be needed. I expect somewhere somehow I am doing something wrong, even if it worked two weeks ago.

Screenshots (If applicable)

Additional context
I am POSTing, the Authorization header is in place. The Auth header is the exact same for a user’s initial Auth, and that works perfect. The refresh_token is the refresh_token provided at initial auth.

Hi @kmwill23 - a refresh token is meant to only be used once to request a new token. Are you storing then updating the refresh token that is received from the refreshed access token?

This failure is happening the very time I am using the refresh token. My normal process is to use that fresh token once, and replace it with the new one from this call.

What happens if you attempt to use the refresh_token after the active token has expired? I am doing some debugging now, and the call is successful if I use the refresh_token within the 3599 second expiry time.

Likely problem discovered!

We have three developers who are using this account for testing purposes.

  • Dev A authenticates
  • Dev B authenticates

I believe at this point Dev A’s authentication and refresh_token are no longer valid. Sound about right?

So now I have to find a way to allow multiple Devs onto one unpublished API.

Hey @kmwill23,

Correct. If a user reauthorizes the app, or say “Logs in with Zoom” to your app on a different device, it will generate new tokens, invalidating the old ones.

Few ways you can handle this, update the tokens in your DB so it shares the same tokens between the two logins, or show a message to the other user saying they need to login with Zoom again.