search

d3473r / jitsi-keycloak

Login to jitsi with keycloak https://github.com/d3473r/jitsi-keycloak/pkgs/container/jitsi-keycloak
https://github.com/d3473r/jitsi-keycloak
MIT License
54 stars 21 forks source link

Failed token verification on Jitsi 7577-2 #57

Closed devium closed 1 year ago

devium commented 1 year ago

I just upgraded from 7439-2 to 7577-2 and that seems to have broken JWT validation. I get the following error in Prosody:

muc.meet.jitsi:token_verification error Token eyJhbGciOiJIU[...]PZBgw not allowed to join: futurecallsfightthoroughly@muc.meet.jitsi/c3e37956

It seems this is connected to this issue: https://github.com/jitsi/jitsi-meet/issues/11967

Apparently, token verification has changed in one of the recent updates.

devium commented 1 year ago

Actually jitsi-keycloak seems fine. It's just that Prosody now properly validates the sub claim, i.e. the JITSI_SUB variable.

I had it set to jitsi.mydomain.org and apparently it needs to be set to meet.jitsi instead, at least in my Kubernetes setup.