# Web Meeting SDK: Expected error when joining without OBF token after Feb 23

**URL:** <https://devforum.zoom.us/t/web-meeting-sdk-expected-error-when-joining-without-obf-token-after-feb-23/141515>\
**Category:** Web\
**Created:** [January 26, 2026, 6:57pm UTC](https://devforum.zoom.us/t/web-meeting-sdk-expected-error-when-joining-without-obf-token-after-feb-23/141515 "2026-01-26T18:57:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![LeandroSantos](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/leandrosantos/32/73315_2.png) [@LeandroSantos](https://devforum.zoom.us/u/LeandroSantos)\
**Post date:** [January 26, 2026, 6:57pm UTC](https://devforum.zoom.us/t/web-meeting-sdk-expected-error-when-joining-without-obf-token-after-feb-23/141515/1 "2026-01-26T18:57:25Z")

</div>

We are currently transitioning our webinar solution to use **OBF tokens** in preparation for the upcoming enforcement described here:  
[https://developers.zoom.us/blog/transition-to-obf-token-meetingsdk-apps/](https://developers.zoom.us/blog/transition-to-obf-token-meetingsdk-apps/?utm_source=chatgpt.com)

We are using the latest **Web Meeting SDK (v5.1.0)** and would like clarification on the **expected error behavior starting February 23** if a client attempts to join a meeting using **only the legacy SDK signature (without an OBF token)**.

This is important for our implementation because we are building a **fallback mechanism** : if joining with the legacy SDK signature fails, we want to automatically retry using the OBF-based approach. To implement this reliably, we need to understand:

- Which **error codes** (if any) the Web Meeting SDK will return in this scenario, or

- Whether the failure will surface as a **generic join error** or another specific behavior.

Could you please clarify what errors or failure behavior we should expect when attempting to join without an OBF token after the enforcement date?

Thank you in advance for the guidance.

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [January 28, 2026, 10:04am UTC](https://devforum.zoom.us/t/web-meeting-sdk-expected-error-when-joining-without-obf-token-after-feb-23/141515/2 "2026-01-28T10:04:18Z")

</div>

@LeandroSantos these error code should help you here

[https://developers.zoom.us/docs/meeting-sdk/web/client-view/error-codes/#anonymous-join-enforcement--obf-error-codes](https://developers.zoom.us/docs/meeting-sdk/web/client-view/error-codes/#anonymous-join-enforcement--obf-error-codes)

---

<div class="post-metadata">

**Author:** ![developer-whova](https://avatars.discourse-cdn.com/v4/letter/d/43a26b/32.png) [@developer-whova](https://devforum.zoom.us/u/developer-whova)\
**Post date:** [January 28, 2026, 7:41pm UTC](https://devforum.zoom.us/t/web-meeting-sdk-expected-error-when-joining-without-obf-token-after-feb-23/141515/3 "2026-01-28T19:41:41Z")

</div>

Hi, I think it’s simple to add a parameter that will allow us to test these error codes directly. Is there any way you can help pass this feedback, as I presume the logic to enforce these changes is ready?
