Open itdkr opened 1 year ago
Hi itdkr, I had the same error, when I pasted the whole generated JWT code into Nextcloud jitsi integracion instead of the JWT_APP_SECRET configured in jitsi server. When I changed this, everything started to work.
Check the jitsi's web server logs and find the URL which Nextcloud tries to access. There is the JWT code, that you can decode at https://jwt.io/ then you can try to analyze what is wrong.
@itdkr did Djzezza's comment help you solving this?
I made the same mistake, that I entered the generated JWT token (payload + token signed with secret) instead of the JWT_APP_SECRET in the field. I had wondered why the JWT which the app appends to the URL is different than the token I provided.
As we share our Jitsi instance with others, giving away the JWT_APP_SECRET to people who run nextclouds is not ideal from a security perspective. It feels like giving your private key to others. Some will appreciate that the JWT token dialogue in the Jitsi app does the JWT token generation, but this is on the cost of providing a secret to another system.
Proposal: add a field: JWT token
and below have the existing fields with a headline "Or let the app generate the JWT token:" and paste the calculated result into the JWT token field, which is then further being used for authentication.
Hi everyone,
i have a issue with the Nextcloud Jitsi JWT Plugin.
If i connect to the Jitsi conference via Nextcloud i get this issue enclosed.
if i connect to a conference via the Jitsi Webinterface and use a JWT everthing is fine. (i use the same jwt for nextcloud an jitsi)
The log from /var/log/prosody/
Can anyone please help me? Thank you.
Regards itdkr