# AUTHRET\_UNKNOWN (code 5) on Meeting SDK Linux native auth since March 2, 2026

**URL:** <https://devforum.zoom.us/t/authret-unknown-code-5-on-meeting-sdk-linux-native-auth-since-march-2-2026/142270>\
**Category:** Meeting SDK\
**Created:** [March 3, 2026, 2:39pm UTC](https://devforum.zoom.us/t/authret-unknown-code-5-on-meeting-sdk-linux-native-auth-since-march-2-2026/142270 "2026-03-03T14:39:05Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![HaidelBert](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/haidelbert/32/73821_2.png) [@HaidelBert](https://devforum.zoom.us/u/HaidelBert)\
**Post date:** [March 3, 2026, 2:39pm UTC](https://devforum.zoom.us/t/authret-unknown-code-5-on-meeting-sdk-linux-native-auth-since-march-2-2026/142270/1 "2026-03-03T14:39:05Z")

</div>

We’re running a Meeting SDK bot on Linux x86\_64 using SDK version **v6.7.5.7391**. Authentication via `SDKAuth()` with a JWT token was working fine until **March 3, 2026** , when it started returning `AUTHRET_UNKNOWN` (code 5) consistently. No code changes were made.

**Setup:**

- Platform: Linux x86\_64 (Docker container)

- SDK version: v6.7.5.7391 (latest)

- App type: General app / User Managed

- App status: Draft, **Active for internal users**

- Authentication method: `IAuthService::SDKAuth()` with `AuthContext.jwt_token`

**JWT payload format:**

```auto
{
  "alg": "HS256",
  "typ": "JWT"
}
{
  "appKey": "<Client ID>",
  "iat": <now - 30>,
  "exp": <iat + 86400>,
  "tokenExp": <iat + 86400>
}

```

Signed with Client Secret using HS256.

**What we’ve verified:**

- Client ID (22 chars) and Client Secret (32 chars) are present and correct

- JWT is well-formed (3 parts, valid structure)

- System clock is accurate (no skew)

- The meeting is hosted by a user within the same Zoom account that owns the app

- `InitSDK()` returns `SDKERR_SUCCESS` (0)

- `SDKAuth()` returns `SDKERR_SUCCESS` (0), but the `onAuthenticationReturn` callback returns `AUTHRET_UNKNOWN` (5)

**What we’ve tried:**

- Using `AuthContext.publicAppKey` with Client ID instead of JWT — returns `AUTHRET_JWTTOKENWRONG` (11)

- No code changes from working state last week

**Questions:**

1. Did the March 2, 2026 authorization enforcement change anything about SDK-level authentication via `SDKAuth()` with JWT, even for same-account meetings?

2. Is there a new required JWT payload field or authentication flow for native Linux SDK apps post-March 2?

3. Does a Draft / “Active for internal users” app need any additional configuration to continue authenticating after the March 2 changes?

4. Is `AuthContext.publicAppKey` intended as a replacement for JWT auth on native platforms, and if so, what value should it contain?

Any guidance is appreciated. Happy to provide SDK logs if needed.

---

<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:** [March 4, 2026, 12:38am UTC](https://devforum.zoom.us/t/authret-unknown-code-5-on-meeting-sdk-linux-native-auth-since-march-2-2026/142270/2 "2026-03-04T00:38:58Z")

</div>

@HaidelBert can you capture an SDK log and share it with me?

Tag me in your response please

---

<div class="post-metadata">

**Author:** ![HaidelBert](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/haidelbert/32/73821_2.png) [@HaidelBert](https://devforum.zoom.us/u/HaidelBert)\
**Post date:** [March 4, 2026, 6:54am UTC](https://devforum.zoom.us/t/authret-unknown-code-5-on-meeting-sdk-linux-native-auth-since-march-2-2026/142270/4 "2026-03-04T06:54:08Z")

</div>

@chunsiong.zoom Sure: [https://drive.google.com/file/d/11m05KZQ4YkyM29CZ-x9mYtqll0l1qhR\_/view?usp=sharing](https://drive.google.com/file/d/11m05KZQ4YkyM29CZ-x9mYtqll0l1qhR_/view?usp=sharing)

---

<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:** [March 4, 2026, 7:23am UTC](https://devforum.zoom.us/t/authret-unknown-code-5-on-meeting-sdk-linux-native-auth-since-march-2-2026/142270/5 "2026-03-04T07:23:43Z")

</div>

> [@HaidelBert](#):
>
> AUTHRET\_UNKNOWN

@HaidelBert I’ll need to PM you for more details

---

<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:** [March 5, 2026, 12:01pm UTC](https://devforum.zoom.us/t/authret-unknown-code-5-on-meeting-sdk-linux-native-auth-since-march-2-2026/142270/6 "2026-03-05T12:01:28Z")

</div>

Resolved, there was an issue running Meeting SDK Linux on Docker.

Meeting SDK Linux requires x86/x64 environment

---

<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:** [March 5, 2026, 12:01pm UTC](https://devforum.zoom.us/t/authret-unknown-code-5-on-meeting-sdk-linux-native-auth-since-march-2-2026/142270/7 "2026-03-05T12:01:34Z")

</div>

Closed on March 5, 2026, 12:01pm UTC


