No idea how to use this

[boredomdenied]

Documentation is quite sparse and assumes a lot. There appears to be numerous variations in how to setup jitsi. What are the prereqs for this to work? I see no JWT anything digging through config files on a standard jitsi install. Is this some add-on? What are the additional subdomains referring to? I have a vanilla instance with zero subdomains that seems to be working out.

Having said all of that, I have no idea how to use this whatsoever. Please help me figure this out so I can send a PR to update the readme so other users don't get lost. Thank you

[MarcelCoding]

The README is based on a jitsi setup using docker. The references to jitsi e.g. the docker-compose.yaml are pointing to the .env from jitsi. Basically you have to change the values defined here in the .env from jitsi.

In other words JITSI_SECRET should be the same as JWT_APP_SECRET at the .env from jitsi and JITSI_SUB the same as JWT_APP_ID.

The value ISSUER_BASE_URL is the base URL of your ID Provider. (${ISSUER_BASE_URL}/.well-known/openid-configuration should result in something like a or google)
CLIENT_ID and SECRET is your OpenID Client ID and Secret.
And as last you have to update all URLs.

[boredomdenied]

Thanks for taking the time. This will likely help someone else in the future. I've abandoned this as a time waster and found a workaround. We use GitLab to SSO with Mattermost then use the Jitsi integration. I 404 the lander page for Jitsi. This makes it so someone not in our system would have to get their hands dirty to start or join meetings. The GitLab -> Mattermost SSO is painless and this just works for our needs. Closing this and hope that someone else can make good use of your reply in the future.

Appreciate you taking the time.