Jwt authentification : what could go wrong?

well these are not solutions… but a few issues that kept me from sleeping the last two days, so if something is not working, you might wanna check them out :roll_eyes:

lua dependencies

lua 5.2 or 5.1 ?
basexx
luacrypto (might need libssl1.0-dev)
lua-cjson
luajwtjitsi

prosody version

jitsi-meet-tokens needs prosody-trunk (>= 1nightly747) or prosody-0.11
dpkg -l | grep jitsi to display versions

reading rights of localhost.crt and other cert related issues

Failed to load ‘/etc/prosody/certs/localhost.key’ is the symptom
chmod solves it and in jicofo config changed localhost to my jitsi domain, didn’t hurt
prosodyctl cert generate in some other cases

the prosody cfg.lua file

https://github.com/jitsi/lib-jitsi-meet/blob/master/doc/tokens.md#patching-prosody
I wonder if a component has to be declared for jvb? did it, didn’t hurt…

focus and jvb user/password declarations

i tried so much things that at some point focus and/or jvb weren’t declared as admins or with wrong passwords (to be found in config files in /etc/jitsi/jicofo/ and /etc/jitsi/videobridge/ directory, along with the sip-communicator.properties files (are those to be amended?)

storage, none or memory?

still don’t sure, depend on prosody version? went with none

is my token valid?

http://jwt.io :wink:

and then, :clinking_glasses: :joy:

I’m banging my head on this one too. did you get a working setup? I’m starting to wonder if my problem isn’t with prosody 11.5…what vers of prosody are you running?

ic prosody 0.10.0-1build1
rc prosody-0.11 1nightly85-1~bionic
ii prosody-trunk 1nightly1250-1~bionic
:sweat_smile:
It was working, then it wasn’t… when I apt upgraded the jitsi-meet-prosody package:
ii jitsi-meet-prosody 1.0.3992-1
I had to change storage to memory… (i thought i had set it to none but it was null when I checked :face_with_raised_eyebrow:)

any chance you could post a sample of your configs to get this working?