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

Meeting SDK Android
1

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.

2

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

3

@e2cvideo could you use a valid epoch time?

The epoch time in your token is not a valid time.
image

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

4

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

ZSEE-120784

5

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

6

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.

7

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!

8

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?

9

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

10

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

Please help ASAP.
Amir

11

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”.

12

@e2cvideo

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

13

@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

14

Hello, any news about this issue?

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

15

@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.

16

Can you give us an update about our critial problem?

17

@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.

18

@amir could you check if it is resolved now?

19

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