Is JWT as authenticator broken for Reservations in Jitsi-Docker?

I have a simple setup of Jitsi in Docker, using JWT-tokens for authentication. That part is working fine.
But the reservation system get’s some bad requests from Jitsi when it tries to start the conference.

The payload in JWT is like
“avatar”: “https:/”,
“name”: “John Doe”,
“email”: “”,
“id”: “abcd:a1b2c3-d4e5f6-0abc1-23de-abcdef01fedcba”
and will authenticate the user. But then the reservation system get a request from Jitsi with a payload like:
According to, the value of “mail_owner” is “if authentication system is enabled this field will contain user’s identity” - but it is being set to an UUID@meet.jitsi, and not the e-mail provided in JWT. Nor do it use the ID set in JWT payload. In the doc it says that both “email” and “id” are valid, but where do they go?
Since the reservation system don’t recieve some email-address/ID/UUID that connects the user with the conference, it rejects it. Is this a bug, or am I missing something? Is there a way to get the authenicated users ID/email from Jitsi by asking with the mail_owner value?

@Johan_Lundqvist Did you ever find a solution for this? I am finding myself geeting the same error when I enable authentication with the reservation system. Thanks!