Hi, I would like to request an increase to our OAuth token index tolerance to 2 for a server-to-server OAuth app called “Virtual Scheduler” (just created today on our account). The email that I created this account with is the one listed on this application. Thank you
Hi @jlsingleton
Thanks for reaching out to the Zoom Developer Forum, I am happy to help here!
I have created a support ticket on your behalf and you should be hearing from our team soon.
Cheers,
Elisa
1 Like
Hi Elisa, Thank you so much! I have not located any zoom documentation or examples within the OAuth2.0 Framework (rfc6749) of how to utilize the token_index. We have proof of concepts working with the default single token index, but can you point me in the right direction for an example when more than 1 token index is being used? Thank you!
Hey @john
We are working on creating the docs for this feature and releasing them, I will make sure to share them with you when they are live.
In the meantime, if you already have a higher token tolerance in your app, the main thing that changes is just an extra query parameter in your request when requesting an Oauth token.
For example:
https://zoom.us/oauth/token?grant_type=account_credentials&account_id={accountId}&token_index=0
This request will generate a token in index 0, so you can go ahead and send a second request like this:
https://zoom.us/oauth/token?grant_type=account_credentials&account_id={accountId}&token_index=1
this will generate another token at index 1, the importance of this feature is that token at index 0 won’t be invalidated and you will be able to have 2 tokens working at the same time.
The default behavior is that when you create a new token, the previous one gets invalidated.
Hope this helps!
Elisa