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/
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.