Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

token_verification error after update

See original GitHub issue

Description:

If I upgrade a JWT enabled Jitsi installation on Ubuntu 20.04.4 LTS from

ii jitsi-meet 2.0.7439-1 all WebRTC JavaScript video conferences
ii jitsi-meet-prosody 1.0.6260-1 all Prosody configuration for Jitsi Meet
ii jitsi-meet-tokens 1.0.6260-1 all Prosody token authentication plugin for Jitsi Meet
ii jitsi-meet-web 1.0.6260-1 all WebRTC JavaScript video conferences
ii jitsi-meet-web-config 1.0.6260-1 all Configuration for web serving of Jitsi Meet
ii jitsi-videobridge2 2.2-9-g8cded16e-1 all WebRTC compatible Selective Forwarding Unit (SFU)
hi prosody 0.11.13-1~focal1 amd64 Lightweight Jabber/XMPP server

to the current version 2.0.7577, JWT authentication is no longer working. In the Prosody log, I see this type of error:

token_verification error Token eyJ0eXAi..... not allowed to join

I did not update Prosody to 0.12.X, as this was not working before.

Do I need to update any config settings?

Issue Analytics

State:
Created a year ago
Reactions:3
Comments:16 (6 by maintainers)

Top GitHub Comments

3reactions

damenchocommented, Aug 19, 2022

You can set enable_domain_verification = false and it will work.

This is duplicate of https://github.com/jitsi/jitsi-meet/issues/11999 I will try to look at it next week.

The mix of jwt and guest domain was bever intended to work together. If that is the case it can be broken at anytime. While refactoring the authentication logic as a whole, we will take in mind this usecase and will offer a solution for it.

2reactions

kiliankollercommented, Aug 6, 2022

We have a setup, where moderators with tokens should be allowed to create rooms, but guest should only be allowed to join existing rooms.

This was deeply discussed here: https://community.jitsi.org/t/jwt-tokens-and-guest-access/18119

The solution with the guest VirtualHost seemed to be the only solution for this case, which worked perfectly for us for years now.

What could be the breaking change in the last update?

Thanks so much!

Top Results From Across the Web

Troubleshoot Invalid Token Errors - Auth0

Error Message: The ID token cannot be validated because it was signed using the HS256 algorithm and public applications (such as a browser)...

Kenzo Error Fix {Failed (remote: token verification failed ...

It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer....

Troubleshooting 'Token failed verification: signature' errors in ...

Problem: Distribution of Release Bundle to Edge node fails with exception 'Token failed verification: signature'

Token Validation Error - TIBCO Product Documentation

Token Validation Error ; The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, ...

RH-SSO: Error message "Token verification failed"

Issue. RH-SSO access token usage is generating the error message "Token verification failed". Environment. Red Hat Single Sign-On (RH-SSO).