-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
muc_lobby_rooms disabled when jitsi-token-moderation enabled #15
Comments
At first, no, this functionality is newer than the current code. I'll take a look at what can be done. |
@nafem doing exactly that, did you find a workaround? @bryanasdev000 Any idea how to make sure that a user is unique, ie the token is used just once. Can put a check ion email id. Noobie here. |
@adhibhuta I haven't found a workaround yet, currently we are disabling the lobby because token authorisation is more important. A bit off topic but regarding single use tokens, I am generating a token for each user based on the room they are trying to access and the level of authority they have. This plugin then provides moderator status based on the topic they present at that time. |
Any updates? |
Not yet I did not have time to mess with that, for now I am deploying without the muc_lobby_rooms option. PRs are welcome too :D |
I don't know what I changed, but I can use the lobby feature + jitsi-token-moderation (browser and app) 🤔😅 |
@nilsreichardt Can you share your prosody lua config, pls? |
@Fremzy Yes, of course :) https://pastebin.com/r5yCNJP7 |
It is not possible to enable both muc_lobby_rooms and jitsi-token-moderation within the same config.
The config below disables muc_lobby_rooms unless I disable jitsi-token-moderation.
The use case is that moderators should be able to authenticate and be assigned as moderator using a token. Non moderators should still require a token to access but may be required to request access while in the Lobby to prevent them from automatically joining an existing call.
`
VirtualHost "fqd.com"
-- enabled = false -- Remove this line to enable this host
authentication = "token"
app_id="xxx"
app_secret="xxx"
allow_empty_token=false
modules_enabled = {
"bosh";
"pubsub";
"ping"; -- Enable mod_ping
"speakerstats";
"turncredentials";
"conference_duration";
"muc_lobby_rooms";
}
Component "conference.fqd.com" "muc"
storage = "memory"
modules_enabled = {
"muc_meeting_id";
"muc_domain_mapper";
"token_verification";
"token_moderation";
}
admins = { "focus@auth.fqd.com" }
muc_room_locking = false
muc_room_default_public_jids = true
`
Is there a way to enable both muc_lobby_rooms and jitsi-token-moderation?
The text was updated successfully, but these errors were encountered: