Will Android Meeting SDK apps using JWT-based join and ZAK/OBF be affected after March 2?

Hi Zoom team,

I would like to confirm whether the following Android app configuration will continue to work after March 2, especially regarding JWT deprecation and SDK authentication.

App configuration:

  • Android application
  • Using Zoom Meeting SDK
  • No Zoom account login (guest join)
  • Users join meetings by entering:
    • Meeting ID
    • Passcode
    • Display name
  • SDK join is performed using a JWT-based SDK signature (Client ID / Client Secret)
  • The app joins meetings hosted by other Zoom accounts

Questions:

  1. After March 2, will this type of SDK-based meeting join (JWT-signed SDK join without Zoom account login) still be supported?
    Or is migration to another authentication method (such as OAuth or Server-to-Server OAuth) required for this use case?

  2. If we plan to use ZAK or OBF with the Zoom Meeting SDK (for example, to start or join meetings with additional permissions),
    is it mandatory to have our own backend server to securely generate and manage these tokens?

  3. In a Zoom SDK app, if a user is logged in with a free Zoom account,
    is it possible for that user to join a meeting hosted by a paid Zoom account (Pro/Business/Enterprise)?

Our app does not authenticate Zoom users for hosting meetings; it is only used to join existing meetings.

Thank you very much for your clarification.

Hi @Zoom74 since the app is joining a meeting hosted by another (external) Zoom account, it is subject to these changes.

It is not mandatory.

Yes.

Please see the following resource for more details:

Hi Zoom team,

Thank you for your previous clarification. I would like to ask a few additional questions:

1.In the official Zoom application, will it continue to be possible for users to join meetings hosted by others without logging into a Zoom account?

2.If we develop an application using the Zoom Meeting SDK that handles the exchange of Authorization Code, Access Token, Refresh Token, ZAK, and OBF between the app and Zoom servers, would such an implementation have any issues during the Zoom Marketplace review process?

Thank you again for your support and clarification.