Join failing when using new App Client ID/Secret instead of legacy SDK keys

Meeting SDK Web
1

Hi everyone,

We are attempting to switch from Legacy SDK Keys to the new App Client ID/Secret to generate meeting signatures and allow our Meeting SDK to join the meeting.

We found that the new App Client ID/Secret does now work with external meetings but works on internal meetings. It generally behaves as if the App is not published.

Manual Testing Results:

  1. Using Legacy SDK Keys on Internal Meetings: Works as expected
  2. Using Legacy SDK Keys on External Meetings: Works as expected
  3. Using production App Client ID/Secret on Internal Meetings: Works as expected
  4. Using production App Client ID/Secret on External Meetings: [FAILS] Does not work

Does anyone have any insights and/or can help with this issue?

Edit:@yoon.conner for visibility. Thank you!

Issue migrating legacy meeting SDK key and secret
2

Hey @StarKee
Thanks for sharing this with us. We are currently looking into this.
Can you please share what errors you are seeing? any logs or meeting IDs where you have experienced this so we can track this further?

3

Hi @elisa.zoom,

Thank you so much for helping us with this.

I am testing with the meeting ID: 86440617274. I have tried it with other meeting IDs and other external accounts before with the same result.

I am not getting any errors on the signature generation step but I am getting the “Signature is invalid“ error on the join step:

Here is how it looks on the UI:

Noting that I am currently using web sdk version 4.0.0 but I have tried it with 5.1.2 before and couldn’t join with the new client id/secret there as well. I have made sure to remove the sdkKey field in both the signature generation and the join function.

1 Like
4

Thanks @StarKee
We are looking into this. I will keep you updated

1 Like
5

Hi @elisa.zoom

Just checking in if there are any updates on this?

Also, just wondering but is it possible to get an extension on the legacy SDK Key deprecation if the issue is not resolved by then? Thanks!

6

I will get back to you with an update soon @StarKee
Have you been able to test again with client id and secret?

7

@elisa.zoom

Hi Elisa, I just tested today and it seems that the new client id/secret works now for external meetings! Thank you so much to the zoom team for looking into this and fixing the issue :folded_hands:

Wondering if things are stable now on Zoom’s end that we can start using the new credentials in production environment? Or would you advise to put that on hold?

8

Hi @StarKee
Happy to hear all is working on your end with the new credentials
Yes, you should be able to continue using new credentials in production environment as best practice.