Web-app-jitsi Role

Description: Self-hosted WebRTC platform for end-to-end-encryptable video conferencing with federated authentication

Variables

• author: Kevin Veen-Birkenbach

• description: Self-hosted WebRTC platform for end-to-end-encryptable video conferencing with federated authentication

• license: Infinito.Nexus Community License (Non-Commercial)

• company: Kevin Veen-Birkenbach https://www.veen.world

• galaxy_tags: [‘jitsi’, ‘meet’, ‘video’, ‘conferencing’, ‘webrtc’, ‘docker’]

• issue_tracker_url: https://s.infinito.nexus/issues

• min_ansible_version: 2.9

• platforms: [{‘name’: ‘ArchLinux’, ‘versions’: [‘all’]}, {‘name’: ‘Debian’, ‘versions’: [‘all’]}, {‘name’: ‘EL’, ‘versions’: [‘all’]}, {‘name’: ‘Fedora’, ‘versions’: [‘all’]}, {‘name’: ‘Ubuntu’, ‘versions’: [‘all’]}]

README

Jitsi Meet

Description

Jitsi Meet is an open-source, end-to-end-encryptable video conferencing platform. Rooms run over WebRTC with a central Selective Forwarding Unit (jvb), an XMPP server (prosody) for signalling, and a conference focus daemon (jicofo).

Overview

This role deploys the official jitsi/{web,prosody,jicofo,jvb} images as a single-domain Jitsi Meet stack. Authentication is bridged to the central Keycloak via JWT (prosody validates RS256 tokens whose issuer is the realm’s OIDC endpoint), and to OpenLDAP via prosody mod_auth_ldap2 in the LDAP-only matrix variant. The web container sits behind the central openresty reverse proxy at jitsi.call.{{ DOMAIN_PRIMARY }}; the media plane (jvb) publishes UDP 10000/udp on the host.

Cosmos

The diagram places Jitsi Meet in the Infinito.Nexus cosmos: the components it deploys (capabilities), the central services it consumes (dependencies), and its outward reach (federation and bridged external networks).

flowchart LR
    subgraph deps [Dependencies]
        dep_svc_db_openldap["svc-db-openldap 🐳🐝"]
        dep_web_app_dashboard["web-app-dashboard 🐳🐝"]
        dep_web_app_keycloak["web-app-keycloak 🐳🐝"]
        dep_web_app_matomo["web-app-matomo 🐳🐝"]
        dep_web_app_prometheus["web-app-prometheus 🐳🐝"]
        dep_web_app_stalwart["web-app-stalwart 🐳🐝"]
        dep_web_svc_css["web-svc-css 💻"]
        dep_web_svc_logout["web-svc-logout 🐳🐝"]
    end
    subgraph role [web-app-jitsi 🐳🐝]
        svc_sso["sso"]
        svc_ldap["ldap"]
        svc_logout["logout"]
        svc_dashboard["dashboard"]
        svc_matomo["matomo"]
        svc_prometheus["prometheus"]
        svc_email["email"]
        svc_css["css"]
        svc_javascript["javascript"]
        svc_jitsi["jitsi"]
        svc_web["web"]
        svc_prosody["prosody"]
        svc_jicofo["jicofo"]
        svc_jvb["jvb"]
        svc_tor["tor ❌"]
    end
    subgraph dependents [Dependents]
        dpt_web_app_matrix["web-app-matrix 🐳🐝"]
    end
    dep_svc_db_openldap -. "0..1" .-> svc_ldap
    dep_web_app_dashboard -. "0..1" .-> svc_dashboard
    dep_web_app_keycloak -. "0..1" .-> svc_sso
    dep_web_app_matomo -. "0..1" .-> svc_matomo
    dep_web_app_prometheus -. "0..1" .-> svc_prometheus
    dep_web_app_stalwart -. "0..1" .-> svc_email
    dep_web_svc_css -. "0..1" .-> svc_css
    dep_web_svc_logout -. "0..1" .-> svc_logout
    svc_sso -. "0..1" .-> dpt_web_app_matrix

Solid 1:1 edges are fixed relationships; dashed 0..1 edges are conditional (enabled only in matching deployments); red 0..0 edges are turned off in this role. Node markers show the role’s deploy modes (💻 host, 🐳 compose, 🐝 swarm); ❌ marks a service that is explicitly turned off, and ⚙️ an Ansible role dependency declared in meta/main.yml.

Features

• JWT-bridged SSO: Prosody validates Keycloak-issued RS256 tokens via JWKS so the OIDC client controls room moderation rights.

• LDAP direct-bind variant: meta/variants.yml V3 wires prosody’s mod_auth_ldap2 against svc-db-openldap for a non-OIDC LDAP-only deploy.

• Three persona surfaces: guest lands on the public landing without a room, biber joins a JWT-issued room, administrator is moderator with token-gated kick/lock.

• Self-contained Prosody: Component secrets for jicofo, jvb, jigasi and jibri are pre-generated via meta/secrets.yml so XMPP auth is stable across redeploys.

Quick Setup

Development

Clone, set up the workstation, and deploy Jitsi Meet onto the local stack:

git clone https://github.com/infinito-nexus/core.git
cd core
make onboard
make compose-deploy mode=reinstall apps=web-app-jitsi full_cycle=false

Production

Run the published image to provision the inventory and deploy Jitsi Meet to a managed server (the mounted volume persists the inventory):

APP=web-app-jitsi
HOST=<your-server>
DOMAIN=<your-domain>
TLS_MODE=self_signed
SSH_PUBLIC_KEY="<your-ssh-public-key>"

docker run --rm -it \
  -v "$PWD/inventories:/etc/infinito.nexus/inventories" \
  -e APP="$APP" -e HOST="$HOST" -e DOMAIN="$DOMAIN" -e TLS_MODE="$TLS_MODE" -e SSH_PUBLIC_KEY="$SSH_PUBLIC_KEY" \
  ghcr.io/infinito-nexus/core/debian bash -c '
    INVENTORY=/etc/infinito.nexus/inventories/production
    infinito administration inventory provision "$INVENTORY" \
      --inventory-file "$INVENTORY/devices.yml" \
      --host "$HOST" \
      --include "$APP" \
      --vars "{\"TLS_MODE\": \"$TLS_MODE\", \"DOMAIN_PRIMARY\": \"$DOMAIN\", \"users\": {\"administrator\": {\"authorized_keys\": [\"$SSH_PUBLIC_KEY\"]}}}" &&
    infinito administration deploy dedicated "$INVENTORY/devices.yml" \
      --password-file "$INVENTORY/.password" \
      --diff -vv'

Developer Notes

Variant matrix lives in variants.yml. Service flags, ports, and image pins in services.yml. Credentials declared in secrets.yml.

Persona contract opt-outs

The biber and administrator Playwright personas are gated on services.sso.enabled. When SSO is off, `templates/playwright.env.j2 <./templates/playwright.env.j2>`__ renders PERSONA_BIBER_BLOCKED=true and PERSONA_ADMINISTRATOR_BLOCKED=true. Two reasons:

• V2 (no auth): every service is off; there is no auth chain to drive end-to-end.

• V3 (LDAP only): Jitsi has no in-app HTTP OIDC adapter, so direct prosody mod_auth_ldap2 binds happen inside the XMPP signalling layer when the user joins a room. The persona helpers only model the OIDC redirect chain through Keycloak, so the LDAP-only variant cannot be exercised via the shared persona helpers.

The guest persona is always live (no auth chain assumption) and the canonical-landing baseline test runs unconditionally.

Further Resources

• Jitsi Meet Project

• docker-jitsi-meet (upstream)

• Jitsi prosody plugins (jitsi-contrib)

Credits

Implemented by Kevin Veen-Birkenbach. Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).