Issue migrating legacy meeting SDK key and secret

We just received an email titled “Action required: Migrate Legacy Meeting SDK Key and Secret”. We were not aware of this change. We are currently using the SDK Credentials for SDK authentication and we are using App Credentials for API access (such as OAuth authentication).

We have begun testing migrating over to using App Credentials for the Meeting SDK authentication, but it always returns a tokenWrong error, even though the code logic for generating the JWT has not changed, only the values of the key and secret. This is specifically the result of calling MobileRTC.shared().getAuthService().sdkAuth().

We validated the logic against the instructions and cannot find any issues. Is there a reason why the SDK credentials would work but the App Credentials would not? There is no indication in the migration guide that there is a change to the logic in how JWT tokens should be generated.

1 Like

Bumping this. Hopefully someone at Zoom can respond as the deadline is coming up.

@thinktapwork Are you able to provide your impacted app ID(s) and/or client ID(s)?

Thanks for the replay @AdamKlockars. Would we be able to provide that over email?

@AdamKlockars Hi Adam, can we send this through email? What email should we use?

Tried this again today and it appears to be working. Not sure what the root issue was but seems like this issue can be closed.

1 Like