DevelopingEntitiesWithFuntations

I'm gonna post the contents of the payload for safety as well. For example, I didn't set nbf to 0...

``` { "context": { "user": { "avatar": "https://assets1.cbsnewsstatic.com/hub/i/r/2016/03/11/6c23251d-8ace-457d-a99b-55b7b8141354/thumbnail/1240x1748/60fcbf89ce937196e5a5bfc9f5af3ab2/gettyimages-514174416.jpg", "name": "Dev", "email": "[email protected]" } }, "moderator": true, "iat": 1711474277, "nbf": 1711474297, "exp": 1719363545, "aud": "jitsi-app", "iss": "jitsi-app", "sub": "meet.jitsi", "room": "*"...

> https://github.com/jitsi/jitsi-meet/blob/bb49c92cc40f23d8203173b5b538d5dc789216c9/resources/prosody-plugins/token/util.lib.lua#L47 > > This needs to be configured to RS512. If there is an ASAP key server we default to RS256. > > I don't think we expose a...

Managed to reload it with `prosodyctl --config /config/prosody.cfg.lua restart`, that's the fix, yeah, silly silly default :P

What's the best approach to fix this? To detect the alg instead of relying on defaults?

> To expose a setting to be able to change default in docker. The problem is that it's not part of the prosody/rootfs folder... I wanted to add it like...

How do I expose it then? With a static volume mount / bind mount?

You probably set your MUC domain to another value or you changed your Docker network definition in the `docker-compose.yml` to NOT `meet.jitsi`