cdist-contrib/type/__jitsi_meet_domain
evilham 87cc109bf1
[__jitsi_meet*] Make rooms on different domains not equivalent
This is a backwards-compatible change.

We switch the approach from "treat all domains as if they were the main domain"
to: "each domain has its own prosody settings".

This works perfectly fine, even with secured domains.

There is a caveat with secured domains, in that they use the main domain to log
in; this means that users are shared across all domains (as they were before
this commit).

This is due to jicofo refusing to start meetings from a domain that is not
configured, and it only accepting one domain.

Right now, this is acceptable, however we could want to authenticate against
e.g. different LDAP / IMAP servers in the future, so this would need addressing
at that stage.

Probably the best way to solve it is by patching jicofo, so it accepts starting
conferences from multiple domains and getting that patch upstream.

Sponsored by:   camilion.eu, eXO.cat
2022-04-21 13:20:30 +02:00
..
files [__jitsi_meet*] Make rooms on different domains not equivalent 2022-04-21 13:20:30 +02:00
parameter [__jitsi_meet_domain] Add analytics settings parameter 2022-04-21 13:13:12 +02:00
boolean [__jitsi_meet*] Add parameters for secure domains 2021-05-10 16:40:46 +02:00
gencode-remote 'unbrand' evilham's jitsi types 2021-01-11 14:18:41 +01:00
man.rst [__jitsi_meet*] Make rooms on different domains not equivalent 2022-04-21 13:20:30 +02:00
manifest [__jitsi_meet*] Make rooms on different domains not equivalent 2022-04-21 13:20:30 +02:00