Jitsi and Keycloak SSO integration
Putting Jitsi Meet room creation behind Keycloak with OpenID Connect token authentication, as the Jitsi handbook documents it: the realm and client, Prosody token settings, wait-for-host and the config.js SSO URLs.

Identity providers, telephony, calendars and business systems that the Jitsi handbook documents connecting to a self-hosted Jitsi Meet.
Putting Jitsi Meet room creation behind Keycloak with OpenID Connect token authentication, as the Jitsi handbook documents it: the realm and client, Prosody token settings, wait-for-host and the config.js SSO URLs.
Authenticating Jitsi room creators against OpenLDAP or Active Directory: the Cyrus SASL route for Debian packages, the AUTH_TYPE=ldap settings for Docker, and the filter and TLS choices that trip up AD deployments.
Restricting Jitsi conferences to Matrix room members through the Matrix user verification service, the hybrid Matrix plus JWT mode, and syncing Matrix moderators to Jitsi room owners.
Connecting Jitsi meetings to phones and room systems: Jigasi as the audio-only SIP gateway, Jibri as a video SIP gateway for meeting room devices, and the ports and credentials each needs.
Setting up the OAuth apps a self-hosted Jitsi Meet needs for Google Calendar and YouTube, Microsoft Outlook calendars and Dropbox recording uploads, and who in your organization has to own each app.
Embedding a self-hosted Jitsi Meet in your own portal or application with the IFrame API or React SDK, and what changes compared with embedding meet.jit.si.
Connecting Jitsi to a booking or scheduling system over the documented reservation REST API, so rooms only open when booked and close when their time runs out.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.