Secure domain Configuration in Load balanced JVB environment



I have installed Meet in a load balanced environment (i.e. : Nginx+MeetAPI on a first server (public address), Prosody, jicofo and Jigasi on a second server (private address), Videobridge on a third server (public address for support tcp/443 WebRTC session).

I try to configure the authentication for opening a room with secure domain schema, as describe in the readme guide, Whit the activation of xmpp ldap2 authentication.

That works pretty fine: I can open a new room with my LDAP credential. But when a new user join this room, he has to login too with his credential !!!

As I have understood, new user of an open room doesn’t need to log in with his credential to enter in conference.

Do you have a guide note for such installation ?
How to configure meet for such fonction ?



I suppose you are following this README:, have you done the VirtualHost "" part and adding to config.js anonymousdomain: '',?
This is the part which allow to users to enter the room, if created, without requiring username or password.


Exactly, I follow this guide for secure-domain
This other guide for LDAP :

And this one for HA JVB :

When I run on a unique server, all is OK and works fine…. but when I Apply the confirguration for JVB run on other server, I have to log in with the credential even if the room is already open.


What do you mean by unique server and for JVB run on other server,?


First, I have installed all components on a unique server Inside my company; configured them and implement LDAP authentication. All works fine.

Then I want to open this to Internet, and I have to re-install it :

  • one server NGINX with meet API,
  • one other server PROSODY / JICOFO / JIGASI and
  • another server VideoBridge .
    In this configuration, the authentication works for openning a new room, but, when new user connect to an existing room, it is prompted for entering indentification credential… this behavior did not exist when jitsi-meet run (previously) on only one server.


Did you double check the anonymous domain settings, from my previous post, in prosody and in config.js? This is the only thing that comes to my mind at the moment.
If that is ok, may be enable debug in prosody and see what is the output when the second participant joins.


I have checked again…. and I don’t find anything wrong …
Find next my prosody config

- Plugins path gets uncommented during jitsi-meet-tokens package install - that's where token plugin is located
--plugin_paths = { "/usr/share/jitsi-meet/prosody-plugins/" }

VirtualHost ""
        authentication = 'ldap2'
        --authentication = "anonymous"
        admins = {
        ssl = {
                key = "/etc/prosody/certs/";
                certificate = "/etc/prosody/certs/";
        modules_enabled = {
            "ping"; -- Enable mod_ping
        c2s_require_encryption = false

VirtualHost ""
        authentication = "anonymous"
        admins = {
        --ssl = {
        --       key = "/etc/prosody/certs/";
        --       certificate = "/etc/prosody/certs/";
        modules_enabled = {
                       "ping"; -- Enable mod_ping
        c2s_require_encryption = false

Component "" "muc"
    storage = "null"
    --modules_enabled = { "token_verification" }
admins = {

--Component ""
--    component_secret = "secret"

Component ""
    component_secret = "secret"

And the meet/

/* eslint-disable no-unused-vars, no-var */

var config = {
    // Configuration

    // Alternative location for the configuration.
    // configLocation: './config.json',

    // Custom function which given the URL path should return a room name.
    // getroomnode: function (path) { return 'someprefixpossiblybasedonpath'; },

    // Connection

    hosts: {
        // XMPP domain.
        domain: '',

        // XMPP MUC domain. FIXME: use XEP-0030 to discover it.
        muc: '',

        // When using authentication, domain for guest users.
        anonymousdomain: '',

        // Domain for authenticated users. Defaults to .
        // authdomain: '',

        // Jirecon recording component domain.
        // jirecon: '',

        // Call control component (Jigasi).
        call_control: ''

        // Focus component domain. Defaults to focus..
        // focus: '',

    // BOSH URL. FIXME: use XEP-0156 to discover it.
    bosh: '//',

    // The name of client node advertised in XEP-0115 'c' stanza
    clientNode: '',

    // The real JID of focus participant - can be overridden here
    // focusUserJid: '',




Finaly I find where is the issue…
I have installed Jitsi Meet in a 3 tiers model : web server nginx in a public DMZ, videobridge on a second public DMZ server and all other components on a private DMZ server.

The issue was about the file /etc/jitsi/meet/ which I forger to duplicate on my nginx web server…

Now all works fine.