# Jitsi Meet

## Presentation

Jitsi Meet is a WEBRTC-based video conferencing application, powering the meet.jit.si online service.

Users may install their own instance of Jitsi Meet for private use, in which case, they may use authentication to control the creation of conference rooms.

The official documentation provides instructions on how to configure Jitsi Meet to use Shibboleth, but with a little adaptation, it can work just as fine with LemonLDAP::NG.

## Configuration

### Pre-requisites

In this guide, it is assumed that you have followed the Jitsi Meet quick start and that you have installed Nginx on your Jitsi Meet server first

If you have not done that, the Jitsi Meet installer will not generate a Nginx configuration file for you. This is not a problem is you are already using your own reverse proxy.

### Jitsi Meet configuration

As with the Shibboleth guide, you need to configure `/etc/jitsi/jicofo/sip-communicator.properties`

    org.jitsi.jicofo.auth.URL=shibboleth:default
    org.jitsi.jicofo.auth.LOGOUT_URL=/logout/

This defines the login servlet as `/login/` and the logout URL as `/logout/`

### Jitsi Meet Nginx configuration

In the Nginx configuration that the Jitsi Meet quickstart generated, you must add the following blocks, just like you would in a typical handler configuration file:

     location = /lmauth {
        internal;
        include /etc/nginx/fastcgi_params;
        fastcgi_pass unix:/var/run/llng-fastcgi-server/llng-fastcgi.sock
        fastcgi_pass_request_body  off;
        fastcgi_param CONTENT_LENGTH "";
        fastcgi_param HOST $http_host;
        fastcgi_param X_ORIGINAL_URI  $request_uri;
      }

    # Protect only the /login/ and /logout/ URLs.
    # You may want to change this is your goal is to make the whole Jitsi Meet instance private

    location ~ ^/log(in|out)/ {

    	auth_request /lmauth;
        auth_request_set $lmremote_user $upstream_http_lm_remote_user;
        auth_request_set $lmlocation $upstream_http_location;
        error_page 401 $lmlocation;

        auth_request_set $mail $upstream_http_mail;
        proxy_set_header mail $mail;
        auth_request_set $lmcookie $upstream_http_cookie;
        proxy_set_header Cookie: $lmcookie;

    	proxy_pass http://127.0.0.1:8888;
    }

### Jitsi Meet Virtual host in Manager

Go to the Manager and create a new virtual host for Jitsi Meet.

Configure the access rules.

- Don't forget to configure the /logout/ URL

Configure the following headers.

- mail: $mail
- displayName: $cn

Jitsi meet expects to find a `mail` HTTP header, it will ignore REMOTE_USER and only use the mail value to identify the user.