[Authentication Failed] - Jitsi Meet Token Authentication Problem

Install & Config
#6

OK well the good news is that i can replicate the error as now i have fixed my JWT issue i am having yours now lmao.

Looking into it now

#7

@Kenza_Cohen, How you solved it? what was your’s problem?

FYI, these are my jicofo logs

Screenshot 2020-04-14 at 12.51.21 AM
Screenshot 2020-04-14 at 12.51.21 AM1440×900 58.6 KB

#8

In /var/log/prosody/prosody.log do you see the following?

Apr 13 21:21:11 general warn Error verifying token err:not-allowed, reason:token required?

This is what i am getting now, also what version of trunk are you using?

#9

@Kenza_Cohen
I am having trunk 747, and i don’t see this kind of warn msg in my prosody.log file. I don’t know, when i’ll be able to solve this. I am stick into these kind of problems since last 3 days.

#10

ok so what i just did to get mine working is updated trunk to latest nightly.

Makre sure the plug directory is set correctly to the VHost file

#11

I am also getting this error now, previous problem fixed by using this technique

and now i am getting same error as you, can you please try this ? Token authentication not working with prosody 0.11.0 · Issue #837 · jitsi/lib-jitsi-meet · GitHub

How to authenticate into jitsi-meet with jitsi-meet-tokens
#12

OK so first of all make sure that the LUA Modules have installed, for some reason mine didnt, you’d need OpenSSL installed as well as the LUA modules.

Than give the server a reboot

#13

@Kenza_Cohen i already installed lua modules and openssl. I can’t se anything weird in my logs. Check my logs
Jicofo logs - https://pastebin.com/raw/82Y6jrhq

jvb logs - https://pastebin.com/raw/yLrrGTS6

Prosody logs - https://pastebin.com/raw/SVBmVAmr

#14

What OS are you using?

#15

Also is Presence_Identity added to your LUA modules for your VHost?

#16

Ubuntu 18.04 bionic on AWS

#17

Yep so we are on the same Distro Too :slight_smile:

In the VHost make sure config resembles something like this:

VirtualHost "meet.<your Domain>"
    -- enabled = false -- Remove this line to enable this host
    authentication = "token"
    -- Properties below are modified by jitsi-meet-tokens package config
    -- and authentication above is switched to "token"
    app_id="<your AppID>"
    app_secret="<Your Secret>"
    allow_empty_token = false;
    -- Assign this host a certificate for TLS, otherwise it would use the one
    -- set in the global section (if any).
    -- Note that old-style SSL on port 5223 only supports one certificate, and will always
    -- use the global one.
    ssl = {
            key = "/etc/prosody/certs/<your Domain>.key";
            certificate = "/etc/prosody/certs/<your domain>crt";
    }
    speakerstats_component = "speakerstats.<your domain>"
    conference_duration_component = "conferenceduration.<your domain>"
    -- we need bosh
    modules_enabled = {
        "bosh";
        "pubsub";
        "ping"; -- Enable mod_ping
        "speakerstats";
        "turncredentials";
        "conference_duration";
        "presence_identity";
    }
    c2s_require_encryption = false

Component "conference.meet.<your Domain>" "muc"
    storage = "none"
    modules_enabled = {
        "muc_meeting_id";
        "muc_domain_mapper";
        "token_verification";
    }
    admins = { "focus@<your domain>" }
    muc_room_locking = false
    muc_room_default_public_jids = true
#18

Also i had to do the following:

sudo apt-get install libssl1.0-dev
sudo luarocks install luajwtjitsi
sudo luarocks install luacrypto
sudo apt-get install jitsi-meet-tokens

For some reason not everything was installed by running the command the first time due to errors but as soon as i ran those above i hit reboot then poof it started working

#19

I am having same configuration, i just did one change storage = “null” instead of “none” because it throws lot of error related same like this [Solved] Issue in connectivity after upgrade the jitsi meet

I am still getting this error in my prosody log

general warn Error verifying token err:not-allowed, reason:token required

#20

@Kenza_Cohen

Would you like to take a look yourself? I’ll share pem file via email and you can ssh to that server.

I am not having any problem, this is a testing instance not a prod.

I am really tired with this problem.

#21

If you can give me an hour or so sure!

#22

any update on this thread ?

#23

I don’t know why anyone isn’t answering this thread, I also created this same on github issues. @damencho

#24

The documentation for jitsi authentication is notably bad. It’s probably the biggest thing holding back adoption.

#25

I am shifting to BigBlueButton.org for live collaboration. i was thinking to join jitsi with my own whiteboard system. But i’ve to shift now.