Hello. As this ticket is still open, I thought I should comment here. I’m not sure if this is an issue tracker or a forum because you darn kids keep changing things.
Anyway, I need similar features and I guess I’m going to have to dig in, but I have an awful lot on my plate right now, so… whew! I guess I’m will need the jicofo component for this?
@Fuji Have you done any work on this so far? The typical mechanism for what you’re requesting is authentication / authorization. You authenticate to say “I am who I say I am” and then you define roles or permissions that you hand out (sometimes you group various permissions together into a “role”). So if the system currently only supports authenticated or not (can create a room or not), then the solution is to add an authorization layer, where the server checks the permissions of the authenticated user before executing the action (e.g., create room, join room, etc.) Further, it is also often useful to be able to define groups such that the authorization is restricted by the data, like Betty can join rooms in the “video-chat101” group, or only rooms with the name “video-chat101” … crap, I’m tired and I hope I’m not just adding confusion.
The trick is to add the mechanisms that WE need in a friendly fashion – that doesn’t force it on others. I’m guessing this is all in the
org.jitsi.jicofo.auth package? Could anybody point me to where the server policies are defined? (i.e., “only authenticated users can create a room, etc.”)
Thank you all for this wonderful software!
EDIT: I think what I was trying to get at is that it is very helpful to properly understand the need before designing it – or at least the needs that we should practically expect. I’m doing this to help out during coronavirus quarantine in the states.