# Linux Meeting SDK: SDKAuth succeeds synchronously but onAuthenticationReturn never fires (General app, JWT auth)

**URL:** <https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-succeeds-synchronously-but-onauthenticationreturn-never-fires-general-app-jwt-auth/146313>\
**Category:** Meeting SDK\
**Created:** [September 8, 2026, 11:48pm UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-succeeds-synchronously-but-onauthenticationreturn-never-fires-general-app-jwt-auth/146313 "2026-09-08T23:48:49Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bryan1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bryan1/32/68159_2.png) [@Bryan1](https://devforum.zoom.us/u/Bryan1)\
**Post date:** [September 8, 2026, 11:48pm UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-succeeds-synchronously-but-onauthenticationreturn-never-fires-general-app-jwt-auth/146313/1 "2026-09-08T23:48:49Z")

</div>

Linux Meeting SDK: SDKAuth succeeds synchronously but onAuthenticationReturn never fires (General app, JWT auth)

SDK version: 7.1.5.4434 (Linux, arm64), libmeetingsdk.so  
App type: General app, Meeting SDK enabled under Features \> Embed, “programmatic join” toggle ON, app authorized on the account via Local Test’s “Add app” OAuth flow.  
Environment: Ubuntu 22.04 container (Docker Desktop on Apple Silicon, arm64), outbound internet access confirmed working.

Symptom: IAuthService::SDKAuth(AuthContext&) returns SDKERR\_SUCCESS synchronously, but IAuthServiceEvent::onAuthenticationReturn is never invoked — not with a success code, not with a failure code — even after waiting up to 120 seconds. This happens identically whether the JWT is well-formed and correctly signed, or deliberately invalid, suggesting the response is silently dropped rather than being JWT-content-specific.

JWT structure being sent: Header {“alg”:“HS256”,“typ”:“JWT”}; payload {appKey: , mn, role: 1, iat: now-30s, exp: iat+7200, tokenExp: iat+7200}, HS256-signed with the app’s Client Secret — matches the documented native-platform claim shape.

What’s been ruled out: iat clock skew (backdated 30s per a similar forum resolution); app not authorized (completed Local Test “Add app” flow); programmatic join disabled (confirmed enabled); anonymous-join review requirement (not applicable — testing entirely within our own developer account); wrong meeting number for ZAK-based start (fixed to use the user’s PMI per the user-types doc, no change in SDKAuth behavior as expected); network/connectivity (strace confirms successful connect() to a Zoom IP on port 443).

No diagnostic info available: GetZoomLastError() returns nullptr after timeout. The SDK’s own log file is written but appears to be an encrypted/binary internal format.

Question: What would cause onAuthenticationReturn to never fire at all for a General app’s JWT-based SDKAuth on Linux, given confirmed connectivity and a Local-Test-authorized, programmatic-join-enabled app? Is there an additional account/app-level entitlement beyond “programmatic join” that must be requested/approved before SDKAuth actually completes?

---

<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:** [September 9, 2026, 2:52am UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-succeeds-synchronously-but-onauthenticationreturn-never-fires-general-app-jwt-auth/146313/2 "2026-09-09T02:52:51Z")

</div>

@Bryan1 I’ll investigate this. Meanwhile if you have the SDK logs in ~/.zoomsdk it will be super helpful.

Internal reference ZSEE-213392

---

<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:** [September 9, 2026, 4:52am UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-succeeds-synchronously-but-onauthenticationreturn-never-fires-general-app-jwt-auth/146313/3 "2026-09-09T04:52:17Z")

</div>

@Bryan1 this is a known issue and will be fixed in 7.2 later this month

---

<div class="post-metadata">

**Author:** ![Bryan1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bryan1/32/68159_2.png) [@Bryan1](https://devforum.zoom.us/u/Bryan1)\
**Post date:** [September 9, 2026, 2:40pm UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-succeeds-synchronously-but-onauthenticationreturn-never-fires-general-app-jwt-auth/146313/4 "2026-09-09T14:40:29Z")

</div>

Here are the logs if you would still like them

(Attachment zoom-meetingsdk-sdkauth-log.log is missing)

---

<div class="post-metadata">

**Author:** ![Bryan1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bryan1/32/68159_2.png) [@Bryan1](https://devforum.zoom.us/u/Bryan1)\
**Post date:** [September 9, 2026, 2:42pm UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-succeeds-synchronously-but-onauthenticationreturn-never-fires-general-app-jwt-auth/146313/5 "2026-09-09T14:42:58Z")

</div>

I tried but can’t upload the logs to the support ticket.

---

<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:** [September 11, 2026, 3:41am UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-succeeds-synchronously-but-onauthenticationreturn-never-fires-general-app-jwt-auth/146313/6 "2026-09-11T03:41:30Z")

</div>

@Bryan1 thanks for reporting this.

---

<div class="post-metadata">

**Author:** ![Bryan1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bryan1/32/68159_2.png) [@Bryan1](https://devforum.zoom.us/u/Bryan1)\
**Post date:** [September 23, 2026, 8:52pm UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-succeeds-synchronously-but-onauthenticationreturn-never-fires-general-app-jwt-auth/146313/7 "2026-09-23T20:52:18Z")

</div>

Any news on this? It is getting close to the end of the month and I haven’t seen 7.2 yet.

---

<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:** [September 24, 2026, 5:57am UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-succeeds-synchronously-but-onauthenticationreturn-never-fires-general-app-jwt-auth/146313/8 "2026-09-24T05:57:52Z")

</div>

@Bryan1 there should be a Linux-All with version 7.2 . It comes with ARM and x64 SDKs

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/b/0/b05cd1f9acf0e0f851fb485ec8c1d11aba37c123.png)

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/7/f/7fb76f5d10b9e642a78861cb3d450b4384f021b0.png)

---

<div class="post-metadata">

**Author:** ![Bryan1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bryan1/32/68159_2.png) [@Bryan1](https://devforum.zoom.us/u/Bryan1)\
**Post date:** [September 26, 2026, 8:03pm UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-succeeds-synchronously-but-onauthenticationreturn-never-fires-general-app-jwt-auth/146313/9 "2026-09-26T20:03:59Z")

</div>

Good news! that SDK version works! Thank you

Bad news… I have a new error:  
time=“2026-09-26T19:59:44Z” level=error msg=“Bot 52 failed at create user: Zoom POST /users failed (400): {“code”:3412,“message”:“ **Your request to add a basic user could not be approved at this time because your account has reached the permitted maximum number of 20 basic users.** Please remove existing basic user(s) from your Users list or the Pending Users list before attempting to add another user.”}” source=console

I thought I could create/destroy as many free accounts as needed. But it looks like we have an account limit for free accounts? That seems really confusing.

---

<div class="post-metadata">

**Author:** ![Norma](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/norma/32/71343_2.png) [@Norma](https://devforum.zoom.us/u/Norma)\
**Post date:** [October 6, 2026, 10:45am UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-succeeds-synchronously-but-onauthenticationreturn-never-fires-general-app-jwt-auth/146313/11 "2026-10-06T10:45:26Z")

</div>

I’d check the callback registration and SDK initialization first. Since `SDKAuth()` succeeds but `onAuthenticationReturn` never fires, it may be an event-handling or Linux ARM64 SDK issue rather than the JWT itself.

---

<div class="post-metadata">

**Author:** ![Bryan1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bryan1/32/68159_2.png) [@Bryan1](https://devforum.zoom.us/u/Bryan1)\
**Post date:** [October 7, 2026, 9:03pm UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-succeeds-synchronously-but-onauthenticationreturn-never-fires-general-app-jwt-auth/146313/12 "2026-10-07T21:03:59Z")

</div>

The new build was the solution. I’ve just run into a hard limit in my account of 20 Basic Users. The SDK doesn’t allow you to create more than that. It looks like I will have to work with my Account Rep to get that changed.
