You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just in case someone else was using this library with JWT and has moved to Server-to-server Oauth (v2.x)... this library does not support multi-threaded server applications with Oauth out of the box. By default, Zoom will invalidate any previous oauth tokens when requesting a new one. This library always requests a new token. Thus if you have a multi-threaded or multi-instance server application, you will get random race conditions with "Invalid access token" errors in your logs. See this zoom discussion for more context:
tl;dr
You need to implement your own thread-safe shared token service, and then you can use the onGetAccessToken feature of this library to avoid fetching the token directly from zoom and instead fetch it from your token service.
The text was updated successfully, but these errors were encountered:
Just in case someone else was using this library with JWT and has moved to Server-to-server Oauth (v2.x)... this library does not support multi-threaded server applications with Oauth out of the box. By default, Zoom will invalidate any previous oauth tokens when requesting a new one. This library always requests a new token. Thus if you have a multi-threaded or multi-instance server application, you will get random race conditions with "Invalid access token" errors in your logs. See this zoom discussion for more context:
https://devforum.zoom.us/t/server-to-server-oauth-annoying-token-invalidation/72070/15
tl;dr
You need to implement your own thread-safe shared token service, and then you can use the
onGetAccessToken
feature of this library to avoid fetching the token directly from zoom and instead fetch it from your token service.The text was updated successfully, but these errors were encountered: