Hello @Jer
After OBF rolls out, can the SDK still start meetings using only a ZAK (i.e., without an OBF token in the join flow)?
- To start and join a meeting or webinar for a logged in user both the ZAK+ JWT token are required
- To join a meeting or webinar outside the app owner’s account, JWT + OBF would be required. see: Meeting SDK Auth
For sign-in required conferences, does the ZAK used by the SDK need to be generated for the host user specifically, or can it be any licensed user on the account?
- If you want to start or host a meeting/webinar you would need to pass in the ZAK token , so ZAK must be generated for the user who will be the host. The ZAK essentially says, “The user associated with this key is the host for this specific meeting.”
If the user/account that owns the OBF token leaves the meeting (or is removed), does the SDK session tied to that OBF token lose access or get disconnected?
- The meeting will continue as long as the ZAK is valid . If host wants to leave, they can assign an alternate host to any licensed user in the meeting. The OBF token owner is not a factor in the meeting being connected/disconnected here
Does an OBF token behave differently or carry different privileges depending on the meeting type (standard meeting vs webinar vs other conference types)?
- OBF is used to authorize specific users and is consistent across meeting types (Meeting, Webinar)