# Linux Meeting SDK SDKAuth returns AUTHRET\_JWTTOKENWRONG even with valid General App JWT

**URL:** <https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-returns-authret-jwttokenwrong-even-with-valid-general-app-jwt/144262>\
**Category:** Meeting SDK\
**Created:** [June 17, 2026, 8:21am UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-returns-authret-jwttokenwrong-even-with-valid-general-app-jwt/144262 "2026-06-17T08:21:51Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![akash9](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@akash9](https://devforum.zoom.us/u/akash9)\
**Post date:** [June 17, 2026, 8:21am UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-returns-authret-jwttokenwrong-even-with-valid-general-app-jwt/144262/1 "2026-06-17T08:21:51Z")

</div>

Hello Zoom Team,

We are testing the Zoom Meeting SDK for Linux for a local POC.

**SDK / App setup:**

- SDK: `zoom-meeting-sdk-linux_x86_64-7.0.5.3527`

- App type: General App

- Local Test: Ready and app added/authorized

- Meeting SDK enabled under Embed

- Linux-x86\_64 selected

- Programmatic Join enabled

- Scopes added:

- Client ID starts with: `ojIvQ2...`

- Client Secret length: 32 characters

**Issue:**

SDK initialization succeeds, but SDK authentication fails.

Terminal output:

```auto
InitSDK result=0
CreateAuthService result=0
Auth SetEvent result=0
C++ received JWT length=240
C++ received JWT dot_count=2
SDKAuth result=0
Waiting for SDK auth callback using GLib main loop...
Auth callback onAuthenticationReturn ret=11
SDK authentication failed. AuthResult=11

```

As per the Linux Meeting SDK enum, `ret=11` means `AUTHRET_JWTTOKENWRONG`.

**What we already verified:**

- JWT is signed with `HS256`

- `appKey` matches the General App Client ID

- Client Secret is from the same new General App

- JWT signature validates locally

- C++ receives the full JWT correctly

- `SDKAuth()` call itself returns `0`

- Failure occurs only in `onAuthenticationReturn`

- We tested both:

- We also tested variants with `sdkKey`, but all return `ret=11`

- We tested a fresh extracted Linux SDK folder downloaded from the same app page

- Meeting ID is a real numeric meeting ID, not placeholder text

- This happens before the meeting join step, so ZAK/OBF logic has not yet been reached

**JWT payload example, masked:**

```auto
{
  "appKey": "ojIvQ2...NYBw",
  "mn": "94311453476",
  "role": 0,
  "iat": 1781687431,
  "exp": 1781694631,
  "tokenExp": 1781694631
}

```

**Questions:**

1. Should a General App Client ID/Client Secret authenticate successfully with Linux Meeting SDK v7.0.5.3527 using `SDKAuth()`?

2. Is there any additional backend enablement needed for Linux Meeting SDK authentication?

3. Does the Zoom SDK Universal Credit package need to be purchased/activated before `SDKAuth()` succeeds?

4. Is `AUTHRET_JWTTOKENWRONG` expected if the account does not yet have SDK entitlement activated?

5. For Linux Meeting SDK native C++, should the JWT contain only `appKey`, `iat`, `exp`, `tokenExp`, or should it also include `mn` and `role`?

Please help us identify whether this is a credential/app entitlement issue or a Linux SDK authentication issue.

Regards,  
Akash

---

<div class="post-metadata">

**Author:** ![akash9](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@akash9](https://devforum.zoom.us/u/akash9)\
**Post date:** [June 17, 2026, 8:57am UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-returns-authret-jwttokenwrong-even-with-valid-general-app-jwt/144262/2 "2026-06-17T08:57:43Z")

</div>

Update:

We verified the exact `sdkKey`-only JWT payload and server time.

Payload decoded from the actual JWT being passed into Linux SDK:

```auto
{
  "sdkKey": "ojIvQ2w7SseKabWaFWNYBw",
  "iat": 1781689300,
  "exp": 1781696500,
  "tokenExp": 1781696500
}

```

Payload keys are only:

```auto
sdkKey, iat, exp, tokenExp

```

Server time check:

```auto
date -u: Wed Jun 17 09:42:35 AM UTC 2026
python epoch: 1781689355
python utc: 2026-06-17 09:42:35

```

So the server clock is correct and the JWT is not expired or future-dated.

Result is still:

```auto
SDKAuth result=0
Auth callback onAuthenticationReturn ret=11
SDK authentication failed. AuthResult=11

```

Can Zoom confirm whether the Development Client ID/Client Secret for this General App is valid for Linux Meeting SDK `SDKAuth()` in Local Test mode, or whether there is any backend/app configuration issue?

---

<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:** [June 17, 2026, 11:45am UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-returns-authret-jwttokenwrong-even-with-valid-general-app-jwt/144262/3 "2026-06-17T11:45:10Z")

</div>

@akash9 how does your JWT token looks like?

---

<div class="post-metadata">

**Author:** ![akash9](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@akash9](https://devforum.zoom.us/u/akash9)\
**Post date:** [June 17, 2026, 11:58am UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-returns-authret-jwttokenwrong-even-with-valid-general-app-jwt/144262/4 "2026-06-17T11:58:39Z")

</div>

Our current JWT is an HS256 signed token generated using the General App **Development Client ID** and **Development Client Secret**.

I am not sharing the full JWT/signature publicly, but this is the decoded structure of the exact token passed to `SDKAuth()`:

```auto
{
  "header": {
    "alg": "HS256",
    "typ": "JWT"
  },
  "payload": {
    "sdkKey": "ojIvQ2w7SseKabWaFWNYBw",
    "iat": 1781689300,
    "exp": 1781696500,
    "tokenExp": 1781696500
  }
}

```

Token details:

```auto
JWT length: 203
payload keys: ['sdkKey', 'iat', 'exp', 'tokenExp']
iat: 2026-06-17 09:41:40 UTC
exp/tokenExp: 2026-06-17 11:41:40 UTC
expiration window: 2 hours
server UTC time during test: 2026-06-17 09:42:35 UTC

```

The token format is:

```auto
xxxxx.yyyyy.zzzzz

```

C++ receives it correctly:

```auto
C++ received JWT length=203
C++ received JWT dot_count=2
SDKAuth result=0
Auth callback onAuthenticationReturn ret=11

```

We also tested the `appKey` version earlier:

```auto
{
  "appKey": "ojIvQ2w7SseKabWaFWNYBw",
  "iat": 1781689300,
  "exp": 1781696500,
  "tokenExp": 1781696500
}

```

and the result was also `ret=11`.

So currently both `sdkKey`-only and `appKey`-only payloads fail with `AUTHRET_JWTTOKENWRONG`.

---

<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:** [June 17, 2026, 12:00pm UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-returns-authret-jwttokenwrong-even-with-valid-general-app-jwt/144262/5 "2026-06-17T12:00:21Z")

</div>

@akash9 I’ll PM you for the JWT Token

---

<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:** [June 22, 2026, 8:29am UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-returns-authret-jwttokenwrong-even-with-valid-general-app-jwt/144262/6 "2026-06-22T08:29:27Z")

</div>

solved: iat was set in the future  
solution: ensure that iat in the JWT payload is slightly in the past.

---

<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:** [June 22, 2026, 8:36am UTC](https://devforum.zoom.us/t/linux-meeting-sdk-sdkauth-returns-authret-jwttokenwrong-even-with-valid-general-app-jwt/144262/7 "2026-06-22T08:36:23Z")

</div>

Closed on June 22, 2026, 8:36am UTC


