How to Enable Authentication on a Self-Hosted Jitsi Meet Instance

A default Jitsi Meet installation is open to anyone with the server URL, allowing unauthorized users to create meeting rooms and potentially run up hosting costs. To prevent misuse, administrators can restrict room creation to authenticated users by modifying three configuration files: the Prosody XMPP server config, the Jitsi web frontend config, and the jicofo properties file. The Prosody config must be updated to switch authentication from anonymous to internal_hashed for the primary domain, while a separate guest virtual host is added to allow anonymous users to join existing rooms. The web frontend config requires an anonymousdomain directive pointing to the guest host, and the jicofo component must be updated with an authenticated XMPP URL. Once all changes are saved, the relevant services need to be restarted and user accounts with hosting permissions must be created.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in