Let loadbalancer inject JWT in url for authorized users


We would like to let our loadbalancer handle auth and inject a JWT to jitsi for authorized users by a rewrite of the url and append jwt=XXXXXX.

Unauthorized users will have no network connectivity to jitsi until an authenticated user have started a meeting. Routes to already started meetings are open for everyone by the loadbalancer to allow guests.

We are working on a proof of concept but have not managed to get a working solution.

Is this workflow possible with jitsi and are there any pitfalls to consider?

How does a loadbalancer know if a user needs a token?

What problems have you run into so far?