Reading the documentation, the only interaction between the browser and our server seems to be to generate a signature for a given user. Logically, in my system, certain users should always become: a host, a manager, or a participant and I know at signature generation time what that role should be for that user. Is there supposed to be some way for me to bake that information into the signature so that the browser-side clients don’t have to renegotiate / hand-off roles?
The browser is typically not considered a secure context so it would seem to me a strange pattern to let the browsers decide what role should be assigned to a given user (along with the associated authority to do stuff) with respect to a Zoom meeting.
For a given meeting ID lets say I know which user should ultimately be the host. I’d like the implementation on our browser to act like a waiting room whenever neither the host nor a manager is on the meeting, and I’d like for the meeting to effectively end for all the participants if neither the host nor a manager is in the meeting (effectively kicking participants back into waiting room mode).
I’m hoping someone can help me better understand the underlying philosophy of the Web Video SDK in this regard and help me to understand how to apply that philosophy to reach my goals.