JWT - Package jitsi-meet-tokens still required?

I haven’t updated my installation for quite a while now and was just about to do it. When noticing, that the setup / configuration wasn’t working like it did before (was using jitsi-meet-tokens & “mod_token_moderation.lua”) I checked that the package “jitsi-meet-tokens” hasn’t adopted my prosody configuration file like it did before (e.g. set authentication = “token”, app_id & secret etc.). Furthermore jwt seams to work “out of the box”: username and profile picture set in jwt query work without anything else to do.

I haven’t found any informations about it in the handbook (Self-Hosting Guide - Overview | Jitsi Meet). Can someone tell me what has changed here?

I need a setup where only authenticated users may join only a specific room. Furthermore needs the token to handle moderators and participants.

Not sure I fully understand what problem you are facing.

I have a clean jitsi installation. When running apt -y install jitsi-meet-tokens nothing really changes. My old installation (I guess about 1-2 years old, if you’re interessted, I can check the version) got locked to tokens only after installing the package.

Furthermore, since use properties are extrected from token even without this package, I’m asking if it even is required any more.

Just in case you’re interessted, this is the version I was running:

jitsi-meet 2.0.6293-1
jitsi-meet-prosody 1.0.5307-1
jitsi-meet-tokens 1.0.5307-1
jitsi-meet-turnserver 1.0.5307-1
jitsi-meet-web 1.0.5307-1
jitsi-meet-web-config 1.0.5307-1
jitsi-videobridge2 2.1-551-g2ad6eb0b-1
jitsi-meet-tokens/stable 1.0.6260-1 [upgradable from: 1.0.5307-1]

This is a bug and it’s fixed in unstable. For now, you can update the prosody config manually.

Ah, super! Thank you so much! Will the next stable contain this fix? Any schedule, yet?

By the way: thank you guys so much for your great effort!!

Yes and it should be released this week, baring any unexpected issue.