Meeting SDK Type and Version
Meeting SDK Web v3.12.0
Description
In our current Meeting Web SDK implementation we include signature in the join args which specifies whether the user is the host or participant. I’ve recently learned this is not enough in the mobile SDK and that a zak token is required there to enable the user as the host. We want to be consistent in how this is implemented across the 2 SDKs but when I use the zak token in the web SDK, it still wants a signature as well.
So my question is what is the point then of the zak token if I can make the user a host via the signature? Is there any compelling reason to use the zak token here?
Jordan
Jordan,
Thank you for the question.
The ZAK token can be used in the Web SDK as part of the ZoomMtg.join() method. It is required if you are joining a meeting on another account. So if you intend to use your SDK app to host meetings for users on another acount. You would need to obtain and provide the ZAK. If your meeting host is on the same account as your SDK app they only compelling reason is for the webhooks and reports to contain specific user information.
Are you inferring that we can encode arbitrary meta data in the zak token? If so that would solve another issue I am exploring where opening the desktop client from the browser does not accept customerKey on the url.