Upgrade Jitsi to last version: issues with the JWT authentication

Dear all,
we are planning to upgrade our onprem JITSI installation (dedicated Debian 10 VM using JISTI repository). APT provides new update for JICOFO, JITSTI MEET , JISTI VIDEO BRIDGE e OPENJDK.

jicofo/stable 1.0-911-1 all [upgradable from: 1.0-900-1]
jitsi-meet-prosody/stable 1.0.6447-1 all [upgradable from: 1.0.6260-1]
jitsi-meet-tokens/stable 1.0.6447-1 all [upgradable from: 1.0.6260-1]
jitsi-meet-turnserver/stable 1.0.6447-1 all [upgradable from: 1.0.6260-1]
jitsi-meet-web-config/stable 1.0.6447-1 all [upgradable from: 1.0.6260-1]
jitsi-meet-web/stable 1.0.6447-1 all [upgradable from: 1.0.6260-1]
jitsi-meet/stable 2.0.7648-1 all [upgradable from: 2.0.7439-1]
jitsi-videobridge2/stable 2.2-22-g42bc1b99-1 all [upgradable from: 2.2-9-g8cded16e-1]
openjdk-11-jre-headless/oldstable 11.0.16+8-1~deb10u1 amd64 [upgradable from: 11.0.15+10-1~deb10u1]

We have updated all the available packages, jitsi no longer works correctly, specifically it no longer accepts the links where the base64 of the generated JWT is passed. The username and password login screen remains active. In the previous version, however, thanks to the token, authentication took place. What can we verify? Has anything changed with the last update?
thank you

Check prosody logs for errors, do you see any?

Sep 29 18:18:28 mod_bosh info New BOSH session, assigned it sid ‘b000d75d-d3e8-4ab4-bd4d-bb8458cd6d82’
Sep 29 18:18:28 boshb000d75d-d3e8-4ab4-bd4d-bb8458cd6d82 info Authenticated as 25bac669-4571-43ae-b7ab-809951ac691e@meet.domain.com
Sep 29 18:18:29 mod_bosh error Traceback[bosh]: /usr/share/jitsi-meet/prosody-plugins/token/util.lib.lua:344: bad argument #1 to ‘lower’ (string expected, got userdata)
stack traceback:
[C]: in function ‘lower’
/usr/share/jitsi-meet/prosody-plugins/token/util.lib.lua:344: in function ‘verify_room’
…re/jitsi-meet/prosody-plugins/mod_token_verification.lua:62: in function ‘verify_user’
…re/jitsi-meet/prosody-plugins/mod_token_verification.lua:86: in function ‘?’
/usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
(…tail calls…)
/usr/lib/prosody/modules/muc/muc.lib.lua:557: in function </usr/lib/prosody/modules/muc/muc.lib.lua:497>
(…tail calls…)
/usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
(…tail calls…)
/usr/lib/prosody/core/stanza_router.lua:180: in function ‘core_post_stanza’
/usr/lib/prosody/core/stanza_router.lua:127: in function ‘dispatch_stanza’
/usr/lib/prosody/modules/mod_bosh.lua:306: in function ‘func’
/usr/lib/prosody/util/async.lua:127: in function </usr/lib/prosody/util/async.lua:125>
stack traceback:
/usr/lib/prosody/util/async.lua:211: in function ‘run’
/usr/lib/prosody/modules/mod_bosh.lua:448: in function ‘cb_handlestanza’
/usr/lib/prosody/util/xmppstream.lua:182: in function </usr/lib/prosody/util/xmppstream.lua:162>
[C]: in function ‘parse’
/usr/lib/prosody/util/xmppstream.lua:282: in function ‘feed’
/usr/lib/prosody/modules/mod_bosh.lua:134: in function ‘?’
/usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
(…tail calls…)
/usr/lib/prosody/net/http/server.lua:228: in function </usr/lib/prosody/net/http/server.lua:176>
[C]: in function ‘xpcall’
/usr/lib/prosody/net/http/server.lua:108: in function ‘process_next’
/usr/lib/prosody/net/http/server.lua:124: in function ‘success_cb’
/usr/lib/prosody/net/http/parser.lua:177: in function ‘feed’
/usr/lib/prosody/net/http/server.lua:155: in function </usr/lib/prosody/net/http/server.lua:154>
(…tail calls…)
/usr/lib/prosody/net/server_select.lua:915: in function </usr/lib/prosody/net/server_select.lua:899>
[C]: in function ‘xpcall’
/usr/bin/prosody:80: in function ‘loop’
/usr/bin/prosody:90: in main chunk
[C]: in ?
Sep 29 18:18:44 speakerstats.meet.domain.com:speakerstats_component warn A module has been configured that triggers external events.
Sep 29 18:18:44 speakerstats.meet.domain.com:speakerstats_component warn Implement this lib to trigger external events.

You are missing sub field in your jwt.

Which is “sub field”?

(post deleted by author)

Dear Damencho, we have fixed our custom App for Android 12 compatibility. Also, the sub filed has been corrected.
Now, If I try to update our server with the last versions …

jicofo/stable 1.0-934-1 all [upgradable from: 1.0-900-1]
jitsi-meet-prosody/stable 1.0.6600-1 all [upgradable from: 1.0.6260-1]
jitsi-meet-tokens/stable 1.0.6600-1 all [upgradable from: 1.0.6260-1]
jitsi-meet-turnserver/stable 1.0.6600-1 all [upgradable from: 1.0.6260-1]
jitsi-meet-web-config/stable 1.0.6600-1 all [upgradable from: 1.0.6260-1]
jitsi-meet-web/stable 1.0.6600-1 all [upgradable from: 1.0.6260-1]
jitsi-meet/stable 2.0.7830-1 all [upgradable from: 2.0.7439-1]
jitsi-videobridge2/stable 2.2-43-gce94dbb2-1 all [upgradable from: 2.2-9-g8cded16e-1]
lua-basexx/stable 0.4.1-jitsi1 all [upgradable from: 0.3-2]
lua-cjson/stable 2.1.0.10-jitsi1 amd64 [upgradable from: 2.1.0+dfsg-2.1]

… both official Jitsi Mobile App and our Custom Android apps don’t display user webcam / video stream , only the classic logo is displayed. Using web browser works, webcam works. What I can check for this issue?

Thanks