Hello @Jer
Worth clarifying here that the ZAK token is intended for when an needs to join a meeting as a authenticated user and OBF is intended for when an app needs to join with a authenticated user. Also, can I assume the ‘SDK client’ is an app needing to join the meeting as an individual use? If that is the case ..
- The ZAK token can be used to start or join a meeting as a user, however, it sounds like the the SDK client would be joining would be joining on behalf of the host meaning a OBF token would be needed
- Yes, ZAK is used for the join flow but an alternative host needs to assigned if the original host leaves the meeting in order for the meeting to continue. There needs to be a user in the meeting even if the person who granted the ZAK is not an alternate host can continue the meeting.
- Yes, the user (the service account) associated with the ZAK or OBF must also be also in the meeting. Using a service account’s ZAK for app users will not work if the account is not present in the meeting.
To the last point “The OBF token owner is not a factor in the meeting being connected/disconnected here” once the app has successfully joined, the validity or expiry of the ZAK/OBF token does not impact its connection. The app will remain in the meeting as long as there is a host in the meeting. A refresh token might be needed if the app disconnects
Please also see the FAQ addressing some of the questions on ZAK vs OBF : Updates to Meeting SDK Authorization FAQ
If interested in discussing about RTMS as a solution please see RTMS Account Access - How To Get Started or complete the form here Zoom Realtime Media Streams | Zoom
Hope this helps