# Server-to-Server OAuth: annoying token-invalidation

**URL:** <https://devforum.zoom.us/t/server-to-server-oauth-annoying-token-invalidation/72070>\
**Category:** Authentication\
**Created:** [July 12, 2022, 11:00am UTC](https://devforum.zoom.us/t/server-to-server-oauth-annoying-token-invalidation/72070 "2022-07-12T11:00:01Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![MultiplayerSession](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/multiplayersession/32/66446_2.png) [@MultiplayerSession](https://devforum.zoom.us/u/MultiplayerSession)\
**Post date:** [July 27, 2022, 9:17pm UTC](https://devforum.zoom.us/t/server-to-server-oauth-annoying-token-invalidation/72070/5 "2022-07-27T21:17:31Z")

</div>

I’ve sent a request to Developer Support as ticket # 14947692 to allow a maximum index of 3 (allowing 2 sets for key rotation in our production and testing environments).

**Update (17 August 2022)**: Just to set timing expectations, this request from 27 July 2022 is still awaiting approval. If your application release schedule is dependent on this functionality, you might need to explore alternatives that allow you to ship sooner. The first ticket answer I received on 5 August 2022 suggested creating multiple applications, and I had to specifically draw attention again to the index parameter offer described in this thread, so this approval might be tied to the Zoom API release schedule.

---

_[View the full topic](https://devforum.zoom.us/t/server-to-server-oauth-annoying-token-invalidation/72070)._
