# Updates to Meeting SDK Authorization

**URL:** <https://devforum.zoom.us/t/updates-to-meeting-sdk-authorization/138552>\
**Category:** Meeting SDK\
**Created:** [November 6, 2025, 1:47am UTC](https://devforum.zoom.us/t/updates-to-meeting-sdk-authorization/138552 "2025-11-06T01:47:58Z")\
**Posts on this page:** 1\
**Showing post:** 23

<div class="post-metadata">

**Author:** ![joan.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/joan.zoom/32/36823_2.png) [@joan.zoom](https://devforum.zoom.us/u/joan.zoom)\
**Post date:** [December 23, 2025, 11:49pm UTC](https://devforum.zoom.us/t/updates-to-meeting-sdk-authorization/138552/23 "2025-12-23T23:49:11Z")

</div>

> [@ianb](#):
>
> As part of our online platform, we develop online web conferencing solutions for clients that utilise various third party providers. In the case of Zoom, we utilise a ZAK token from our account to allow users of our web app to connect anonymously to a secure Zoom meeting or webinar created in a clients account. Will this no longer be possible? Secondly, how can we test this behaviour before it is planned to be enforced on 23rd February 2026?

Hello @ianb

Our goal is to ensure that the ‘bad taste’ is replaced by the ‘long-term trust’ of a secure platform. We aren’t just factoring in the licenses sold but also the long-term reputation of the developers. We are here to provide guidance and support needed to make this transition a success including for upcoming scheduled meetings.

For you initial question - correct, from February if the meeting is “external” (hosted outside your account), the joining app must be attributed to a user who has authorized the app. The ZAK token is tied to a specific Zoom user account and will not allow the anonymous join. Please also refer to the [FAQs](https://devforum.zoom.us/t/updates-to-meeting-sdk-authorization-faq/139269?ampDeviceId=5813de84-ce2d-4054-bdfa-d80f34b762c9&ampSessionId=1766530236340&_ics=1766530228411&irclickid=~ahc62ZX073UWXV0WYZOWMDEDBAEFBywyomoklbca2ZYPHxpkgc-2&_gl=1*1to3eae*_gcl_au*MTUxMDQyNjY1LjE3NjQwMjUyNDQuMTk4ODY0MTM3NC4xNzY0MDI1MjUzLjE3NjQwMjUyNTM.*_ga*MjI0MjUyMTMuMTc2NDAyMzQ5Mw..*_ga_L8TBF28DDX*czE3NjY1MzAyMzAkbzU5JGcxJHQxNzY2NTMxOTk4JGo2MCRsMCRoMA..) for more on OBF vs ZAK token and which would be the appropriate solution for your use case. For testing, before calling the `join()` function, the app can determine if it is in an Authorized State: **Has Token:** the user has completed OAuth and the app holds a valid OBF/ZAK token or **No Token:** the user is anonymous. A wait/try logic can be used.

Hope this helps

---

_[View the full topic](https://devforum.zoom.us/t/updates-to-meeting-sdk-authorization/138552)._