We are currently in the process of upgrading our Windows Meeting SDK from v5.11.x to 5.14.x
In this upgrade, we have seen and read that the way we authenticate the Zoom SDK is different than how were doing it before.
In the 5.11 version, we did not use a JWT to authenticate the SDK. We just used the appKey and appSecret located in our Zoom SDK app type.
I would like to confirm, out of an abundance of caution, that the new way of authenticating is to generate a JWT token using these credentials, and although the JWT app type is being deprecated for the Zoom API. That the Zoom Meeting SDK apps will still be authenticating via a JWT.
In the 5.11 version, we did not use a JWT to authenticate the SDK. We just used the appKey and appSecret located in our Zoom SDK app type.
In newer version of 5.14.x you will need to authenticate using a JWT Token signed with your appKey and appSecret.
I would like to confirm, out of an abundance of caution, that the new way of authenticating is to generate a JWT token using these credentials, and although the JWT app type is being deprecated for the Zoom API.
Yes thats right. JWT App Type deprecation should not be confused with the JWT Token used to authenticate Meeting SDK
That the Zoom Meeting SDK apps will still be authenticating via a JWT.
Zoom Meeting SDK Apps will be authenticating via a JWT Token, signed by appKey + appSecret found in SDK App Type