# Error 5 internal error code 124 - jwt. error 6 internal error 3023 - sdk key + secret§

**URL:** <https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615>\
**Category:** Android\
**Created:** [February 27, 2024, 2:28pm UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615 "2024-02-27T14:28:55Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![e2cvideo](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/e2cvideo/32/56972_2.png) [@e2cvideo](https://devforum.zoom.us/u/e2cvideo)\
**Post date:** [February 27, 2024, 2:28pm UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/1 "2024-02-27T14:28:55Z")

</div>

Hello,  
Our app was restored after it disappeared while transferring the app account to another. Now the app auth is failing with error 5, internal error 124. nothing we tried help. fail by using jwt token and old auth method - by app key + secret (this result error 6 internal error 3023) (both worked before the transfer)

our users are using sdk version v5.14.5.13410.  
We also tried connecting with the newest version 5.17.6.19119 - same results.

example of jwt:

{  
“appKey”: “jd…”,  
“iat”: 1709042147,  
“exp”: 1719042147,  
“tokenExp”: 1719042147  
}

Please advise.

---

<div class="post-metadata">

**Author:** ![amir](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amir/32/4414_2.png) [@amir](https://devforum.zoom.us/u/amir)\
**Post date:** [February 27, 2024, 2:32pm UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/2 "2024-02-27T14:32:28Z")

</div>

This is very urgent as our users can’t access our sdk app anymore.  
Tnx

---

<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:** [February 28, 2024, 6:12am UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/3 "2024-02-28T06:12:47Z")

</div>

@e2cvideo could you use a valid epoch time?

The epoch time in your token is not a valid time.  
 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/d/6d9078624591baf7c9a83f6669f406d761e6cbc9.png)

exp and tokenExp needs to be \> 30 mins and \< 2 days from iat as well.

---

<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:** [February 28, 2024, 6:27am UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/4 "2024-02-28T06:27:08Z")

</div>

@amir @e2cvideo I’ve raised a ticket internally for your issue. I’ll update you when i get more details on it.

ZSEE-120784

---

<div class="post-metadata">

**Author:** ![amir](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amir/32/4414_2.png) [@amir](https://devforum.zoom.us/u/amir)\
**Post date:** [February 28, 2024, 6:32am UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/5 "2024-02-28T06:32:41Z")

</div>

Hi Chun, we can’t access our SDK app even with the old auth method (not with JWT but with the app key and app secret inside our app).  
also, when we try to access another new SDK app (not approved one) we can pass the authorization. so it isn’t a problem on our side.  
Please confirm if we need to fix it on our side or this is something on your side.  
Tnx for your urgent support.  
Amir

---

<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:** [February 28, 2024, 6:42am UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/6 "2024-02-28T06:42:46Z")

</div>

> Hi Chun, we can’t access our SDK app even with the old auth method (not with JWT but with the app key and app secret inside our app).

Authenticating directly by passing in SDK Key and SDK Secret has been removed in version 5.14.10

You will need to sign your own Auth Token using the SDK Key and SDK Secret.

> Hi Chun, we can’t access our SDK app even with the old auth method (not with JWT but with the app key and app secret inside our app).

The issue seems to be related to the disappearance and transferring it back.  
Newly creating application would not have this issue

> Please confirm if we need to fix it on our side or this is something on your side.

I can’t confirm yet, but this is probably something we can fix from our side.

---

<div class="post-metadata">

**Author:** ![amir](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amir/32/4414_2.png) [@amir](https://devforum.zoom.us/u/amir)\
**Post date:** [February 28, 2024, 6:48am UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/7 "2024-02-28T06:48:44Z")

</div>

Hi, we checked the epoch time is valid. we set it for 45 hours and it is \< 2 days as you requested. please confirm this isn’t the problem.  
Our production users are using meeting sdk version v5.14.5.13410 that can connect using the old authorization method, and we are able to connect with the old method to our new temp SDK app.  
please help us ASAP as our users can’t use the system for 3 days already!

---

<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:** [February 28, 2024, 6:52am UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/8 "2024-02-28T06:52:49Z")

</div>

> Hi, we checked the epoch time is valid. we set it for 45 hours and it is \< 2 days as you requested. please confirm this isn’t the problem.

Could you remove the quotes from the epoch time?  
iat and exp is enclosed in double quotes

> Our production users are using meeting sdk version v5.14.5.13410 that can connect using the old authorization method, and we are able to connect with the old method to our new temp SDK app.

That’s right. However these users on 5.14.5 cannot connect to the original published app right?

---

<div class="post-metadata">

**Author:** ![amir](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amir/32/4414_2.png) [@amir](https://devforum.zoom.us/u/amir)\
**Post date:** [February 28, 2024, 6:55am UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/9 "2024-02-28T06:55:18Z")

</div>

correct, no one can connect to the original published app (that was restored following the account transfer).  
please help ASAP.

---

<div class="post-metadata">

**Author:** ![amir](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amir/32/4414_2.png) [@amir](https://devforum.zoom.us/u/amir)\
**Post date:** [February 28, 2024, 7:11am UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/10 "2024-02-28T07:11:21Z")

</div>

we also tried without double quotes and it isn’t working.  
see following JWT:  
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhcHBLZXkiOiJwcTQ3TkN6NmhnUnhNWDV1NVV1eDZJd21GWUtFTVVDaHpLQkkiLCJzZGtLZXkiOiJwcTQ3TkN6NmhnUnhNWDV1NVV1eDZJd21GWUtFTVVDaHpLQkkiLCJpYXQiOjE3MDkxMDQxNDIsImV4cCI6MTcwOTI2NjE0MiwidG9rZW5FeHAiOjE3MDkyNjYxNDJ9.VVZ0PLkHzQFSZ6h1W7JkWwlbGAONvI2B6zdK6ofyePU

Please help ASAP.  
Amir

---

<div class="post-metadata">

**Author:** ![e2cvideo](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/e2cvideo/32/56972_2.png) [@e2cvideo](https://devforum.zoom.us/u/e2cvideo)\
**Post date:** [February 28, 2024, 9:19am UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/11 "2024-02-28T09:19:03Z")

</div>

We were not able to connect with the new app this morning " Virtual Club" (Error: 6, internalErrorCode=3023 by old auth / error 5 internalErrorCode 124 by jwt)- we resolved this issue by regenerate the app secret.

Update: after resubmit the app for review - the error came back, cannot connect again. could it be related to the review process?

We tried to regenerate the secret for the old original app - “E2C Digital Club”  
that didn’t fixed the issue.

We need your urgent support to be able to access our original app “E2C Digital Club”.

---

<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:** [February 28, 2024, 10:26am UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/12 "2024-02-28T10:26:31Z")

</div>

@e2cvideo

We are aware of the issue, and working to fix it from our backend

---

<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:** [February 28, 2024, 10:28am UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/13 "2024-02-28T10:28:12Z")

</div>

@e2cvideo @amir just to keep you updated on the summary.

We are aware of the issue, and will be rolling out a fix. There is no action needed from your side at this moment

---

<div class="post-metadata">

**Author:** ![assembleiavirtual](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/assembleiavirtual/32/40880_2.png) [@assembleiavirtual](https://devforum.zoom.us/u/assembleiavirtual)\
**Post date:** [February 28, 2024, 6:21pm UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/14 "2024-02-28T18:21:35Z")

</div>

Hello, any news about this issue?

Getting the same error “Error 5 internal error code 124”

---

<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:** [February 29, 2024, 2:01am UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/15 "2024-02-29T02:01:16Z")

</div>

@assembleiavirtual , please start a new thread and tag me. While you might get the same error code, the root cause might not be relevant to what you are facing.

---

<div class="post-metadata">

**Author:** ![amir](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amir/32/4414_2.png) [@amir](https://devforum.zoom.us/u/amir)\
**Post date:** [February 29, 2024, 4:42am UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/16 "2024-02-29T04:42:52Z")

</div>

Can you give us an update about our critial problem?

---

<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:** [February 29, 2024, 7:19am UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/17 "2024-02-29T07:19:52Z")

</div>

@amir around 2 hours ago from the time of this post, we have identified the issue. We will be applying a fix on your account, and will let you know once it has been done.

---

<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:** [February 29, 2024, 12:03pm UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/18 "2024-02-29T12:03:27Z")

</div>

@amir could you check if it is resolved now?

---

<div class="post-metadata">

**Author:** ![amir](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amir/32/4414_2.png) [@amir](https://devforum.zoom.us/u/amir)\
**Post date:** [February 29, 2024, 2:09pm UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/19 "2024-02-29T14:09:19Z")

</div>

Yes. i confirm the problem fixed by your change.  
Tnx  
Amir

---

<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 1, 2024, 1:11am UTC](https://devforum.zoom.us/t/error-5-internal-error-code-124-jwt-error-6-internal-error-3023-sdk-key-secret/104615/20 "2024-03-01T01:11:28Z")

</div>

Closed on March 1, 2024, 1:11am UTC


