In general it works, if I url encode my room name in the JWT. So, I have as room name “for demo”. JWT will have now “for%20demo” and it works.
BUT, if I put some other special chars like german umlaute (äöüÄÖÜß) it get strange.
Example without a blank: room name = “abcdefäöüßende”
In /usr/share/jitsi-meet/prosody-plugins/token/util.lib.lua, adding logging information:
Apr 06 09:29:06 general info Room: abcdef%25e4%25f6%25fc%25dfende
Apr 06 09:29:06 general info AuthRoom: abcdefäöüßende
So the room is ISO_8859_1 encoded? And the percent char is escaped (twice)?
If I do this hack in JWT too, so I generate url encode with ISO_8859_1 plus substituting % with %25, it will work.
I can go into the room as organisator.
With “secure domain” setup a guest will not join my room. If I enter the room name from above “abcdefäöüßende” into the meet form,
the meet url is just the same https://my domain/abcdefäöüßende
But I get the information, the organisator is not here and I get a room name “abcdef%c3%a4%c3%b6%c3%bc%c3%9fende”
So it seems, here UTF-8 is used.