Hello Zoom Developer Support Team, We run a meeting recording / note-taking bot built on the Zoom Meeting SDK for Web. The bot launches a headless Chromium and calls ZoomMtg.join(...) with an OBF (On-Behalf-of) token that we obtain from GET /users/{userId}/token?type=onbehalf&meeting_id={meeting…

I don’t see a doc-backed reason that desktop joins should behave differently here. You can try looking into two things: Verify the desktop client user is signed in as the exact same Zoom user ID used to generate the OBF token, not just the same display name. If it’s a different signed-in account,…

@amanda-recallai Hi Amanda, Thank you very much for taking a look and replying. Since this behavior seems to depend on how the authorized Zoom user joins the meeting, and may be related to OBF / Anonymous Join Enforcement behavior on Zoom’s side, we would really appreciate confirmation from the Z…

@joan.zoom @ticorrian.heard Hi Zoom Developer Support Team, I would like to follow up on this issue, as we have not yet received a response from Zoom. We have now received another customer report that appears to be the same or a closely related behavior. In the customer environment, multiple user…

Hi @nk1516 Apologies for the wait here. I can consult with our engineering team regarding this issue. Could you provide the meeting id of the meeting where this issue occurred?

@ticorrian.heard We are experiencing the same issue on our side as well, although with a different user/tenant. Would you mind sending me a DM as well? We can provide the meeting ID where the issue occurred and would appreciate it if your engineering team could investigate our case too.

Hi @tomomi @nk1516 I am currently gather info and testing with engineering in regards to this issue. Would either of you be able to provide the following info from a recent affect meeting: Meeting ID or Meeting UUID DisplayName of the host and meeting bot userID used for obtaining the OBF Token T…

@nk1516 we can’t reproduce you issue. and the meeting number have many meeting. could you test an meeting and use this api in console ZoomMtg.getCurrentMeetingInfo({success:function(e){console.log(e)}}) you can get zoom meeting mid. or export HAR file to use when have 4017. here is how to generat…

[Meeting SDK Web 6.0.0] Error 4017 "Authorized user not in meeting" appears only when the authorized user joins from the Zoom desktop app (browser / mobile join works for the same user)

Meeting SDK Web

tomomi (d.tomomi) July 10, 2026, 9:44am 9

@ticorrian.heard @JackYang

We encountered a similar issue again and have therefore created a new topic. At this point, we are not sure whether it is the same issue or a separate one.

We would appreciate it if you could take a look.

Topic		Replies	Views
[Meeting SDK Web 6.1.0] Error 4017 occurs even though the OBF-authorized user is in the meeting Web recording	3	37	July 14, 2026
Zoom Web SDK Error Code 4017 "Authorized user not in meeting" Occurs Even When the Authenticated User Is Already in the Meeting Web	1	36	June 2, 2026
Updates to Meeting SDK Authorization Meeting SDK	32	1409	February 18, 2026
Is there an error code for the case where join with OBF token fails because authorizing user has not yet entered the meeting in Web SDK? Web	0	67	December 10, 2025
How Will ZAK-Based Joins Work After OBF Rollout in the Client SDK? Meeting SDK	9	421	February 13, 2026

[Meeting SDK Web 6.0.0] Error 4017 "Authorized user not in meeting" appears only when the authorized user joins from the Zoom desktop app (browser / mobile join works for the same user)

Related topics