jiti-meet

Commit Graph

Author	SHA1	Message	Date
abora8x8	a5fc75ed35	feat: Dynamically limit the number of participants in a room (#9880 ) * Dynamically limit the number of participants in a room * Remove log	2021-09-09 08:15:14 -05:00
Steve Frécinaux	aff6d4b36d	Fix mod_muc_max_occupants to properly ignore whitelisted users In a typical Jitsi Meet setup, this plugin can be used to limit the number of occupants in a meeting room, while ignoring "utility" users. Such a configuration could be: muc_max_occupants = 2 muc_access_whitelist = { "focus@auth.meet.jitsi"; } It would be expected that this configuration allows two users to attend the meeting room, but in practice only one is allowed, because the whitelist is not honoured. This commit fixes it by actually updating the `user` and `domain` variables being checked. After this change, the scenario above works just fine.	2020-03-31 16:38:23 -05:00
damencho	c9c9f7eac0	Adds max occupant module.	2018-11-03 10:45:59 -05:00

Author

SHA1

Message

Date

abora8x8

a5fc75ed35

feat: Dynamically limit the number of participants in a room (#9880 )

* Dynamically limit the number of participants in a room

* Remove log

2021-09-09 08:15:14 -05:00

Steve Frécinaux

aff6d4b36d

Fix mod_muc_max_occupants to properly ignore whitelisted users

In a typical Jitsi Meet setup, this plugin can be used to limit the number of
occupants in a meeting room, while ignoring "utility" users. Such a
configuration could be:

    muc_max_occupants = 2
    muc_access_whitelist = {
        "focus@auth.meet.jitsi";
    }

It would be expected that this configuration allows two users to attend the
meeting room, but in practice only one is allowed, because the whitelist is not
honoured.

This commit fixes it by actually updating the `user` and `domain` variables
being checked. After this change, the scenario above works just fine.

2020-03-31 16:38:23 -05:00

damencho

c9c9f7eac0

Adds max occupant module.

2018-11-03 10:45:59 -05:00

3 Commits