Jibri cannot record if the token authentication is enabled

Description:

jibri cannot record if the token authentication is enabled and allow_empty_token = false for the latest stable. If I switch back to the anonymous authentication or set allow_empty_token = true then it can record as expected.

Steps to reproduce:

1. Configure jibri and be sure it’s working
2. Install jitsi-meet-tokens package
3. Try to record the meeting session using jibri

Expected behavior:

The meeting session should be recorded when the token authentication is enabled too.

Actual behavior:

jibri is triggered as always but fails in a few seconds.

Server information:

ii  jicofo                1.0-910-1
ii  jitsi-meet            2.0.7577-1
ii  jitsi-meet-prosody    1.0.6380-1
ii  jitsi-meet-tokens     1.0.6380-1
ii  jitsi-meet-turnserver 1.0.6380-1
ii  jitsi-meet-web        1.0.6380-1
ii  jitsi-meet-web-config 1.0.6380-1
ii  prosody               0.11.9-2+deb11u2 amd64

Debian 11 Bullseye

Client information:

Chrome Version 104.0.5112.79 Debian 11 Bullseye

Additional information:

The issue seems related with the following line which was updated for the latest stable. Everything goes back to normal when enable_domain_verification = false is added into the prosody config (in main VirtualHost)

https://github.com/jitsi/jitsi-meet/blob/master/resources/prosody-plugins/token/util.lib.lua#L74

[damencho]

We have taken it offline with @saghul and after discussing it, we decided that the way to go is just to add the jid of jigasi or jibri to the admins of the main muc and that will skip the token verification for those users. https://github.com/jitsi/jitsi-meet/blob/f07bd4a0d6e0765162c8ac4b2290c09438b01a0b/doc/debian/jitsi-meet-prosody/prosody.cfg.lua-jvb.example#L83

[jamesbrooks]

Adding the jitsi to the admins list on the main muc resolved this issue for me also (jitsi w/ jwt). Thanks @damencho!