Android Meeting SDK: Cross-account OBF token join fails with error 124 (works for own account meetings)

Meeting SDK Type and Version

  • Meeting SDK Type: Android Native Meeting SDK

  • SDK Version: 7.0.5.40300

  • Platform: Android

  • Domain: zoom.us


Description

We are using the Zoom Meeting SDK on Android and are experiencing an issue when joining meetings hosted by external Zoom accounts.

Our implementation works successfully when joining meetings that belong to our own Zoom account. However, joins consistently fail for meetings hosted by external institute accounts (isOwnZoomAccount=false).

Current flow:

  1. Call Live Session API with:

    • requiredObfToken=true

    • isWeb=true

  2. Receive:

    • OBF token (ES256)

    • SDK signature/JWT from getSignature?isWeb=true

  3. Initialize Android Meeting SDK using the SDK JWT.

  4. Join meeting using:

    • join_token

    • appPrivilegeToken (OBF token)

    • empty meeting password

Observations:

  • SDK initialization succeeds.

  • Join request succeeds.

  • Connection subsequently fails.

  • The same implementation works for meetings hosted under our own Zoom account.

  • The issue occurs only for meetings hosted by external Zoom accounts.

Additionally, the API response includes a meeting passcode and the Zoom join URL contains a pwd parameter. We are currently not passing the passcode to the Android SDK and are relying on the join token and OBF token.

We would like clarification on:

  1. Whether cross-account joins are supported for this Android Meeting SDK + OBF token flow.

  2. Whether the meeting passcode must still be supplied to JoinMeetingParams.password.

  3. Whether any Marketplace or account-level approval/configuration is required for cross-account joins.

  4. What error code 124 indicates in this scenario.


Error?

SDK initialization:

initialize result = 0

Meeting join request:

joinMeetingWithParams result = 0

Failure:

MEETING_STATUS_CONNECTING
MEETING_STATUS_FAILED
errorCode = 124

No other visible SDK errors are returned.


Troubleshooting Routes

We have already verified:

  • SDK initialization succeeds.

  • Meeting SDK JWT is generated successfully.

  • JWT meeting number claim matches the target meeting.

  • OBF token meeting identifier matches the target meeting.

  • Same Android implementation successfully joins meetings hosted under our own Zoom account.

  • Failure occurs only for meetings hosted by external Zoom accounts.

We can provide the following privately if required:

  • SDK logs

  • Android logcat output

  • SDK App ID

  • JWT payload (redacted)

  • OBF token payload (redacted)

  • Meeting details


How To Reproduce

  1. Authentication method / app type

    • Android Native Meeting SDK

    • SDK JWT authentication

    • OBF token supplied through appPrivilegeToken

  2. Steps

    • Initialize Meeting SDK with valid SDK JWT.

    • Obtain OBF token from backend.

    • Join a meeting hosted by an external Zoom account.

    • Pass join_token and appPrivilegeToken.

    • Leave meeting password empty.

  3. Result

    • SDK initializes successfully.

    • Join request succeeds.

    • Connection fails with error code 124.

  4. Client Type and Version

    • Android application

    • Meeting SDK version: 7.0.5.40300

    • Android OS version: 16

    • Device: Samsung A15

@Wayvida is this app published?

Yes it is published, please find the link below.

Hi @chunsiong.zoom,

Yes, the app is published on the Zoom Marketplace.

Additional information that may help:

  • The issue occurs only for meetings hosted by a specific external Zoom account.

  • The external organization has installed and authorized our Wayvida Live app.

  • The external organization also has the required Zoom license.

  • Meetings hosted under our own Zoom account join successfully using the same Android Meeting SDK implementation.

  • The Android SDK initializes successfully and the join request succeeds, but the connection fails with error 124.

Could you please help verify whether this could be related to:

  • cross-account Meeting SDK authorization,

  • OBF token validation,

  • account-level restrictions, or

  • meeting security settings on the external account?

If needed, we can provide SDK logs, logcat output, app credentials, and token payloads privately.

Thank you.

@Wayvida when you are joining the meeting, are you using either OBF token or user’s ZAK token?

Hi,

We are joining the meeting using an OBF token, not a ZAK token.

Below is the relevant configuration used when joining:

  • meetingId = Id of the Meeting

  • meetingPassword = Password which created on meeting time

  • jwtAPIKey = Client Id of auth App

  • jwtSignature = Generated with credentials

  • obfToken = OBF token created with zoom API

Example:

MeetingOptions(
  meetingId: '<meeting_id>',
  meetingPassword: '<meeting_password>',
  userType: '0',
  jwtAPIKey: '<sdk_key>',
  jwtSignature: '<sdk_signature>',
  obfToken: '<obf_token>',
);

We are not using a user’s ZAK token.

Could you please confirm whether the OBF token flow is the correct approach for joining meetings hosted by external Zoom accounts, and whether there are any additional requirements that could result in error 124?

@Wayvida is the user already in the meeting before the SDK joins?

Hi,

Yes, the meeting has already been started before the SDK client attempts to join.

Our flow is:

  1. The host starts the Zoom meeting.

  2. The participant receives the join details and OBF token.

  3. The Android SDK initializes successfully.

  4. The participant attempts to join using the SDK signature and OBF token.

Despite the meeting already being active, the SDK join fails with error 124 for this external account.

Please let us know if there are any additional requirements regarding the user associated with the OBF token being present in the meeting before the SDK joins.

@Wayvida is the marketplace application published?

Yes it is published, please find the link below.App Marketplace

@Wayvida I’ll PM you for more details