Sign inSign up

galaxy102/jitsi-meet-oidc

By galaxy102

•Updated about 4 years ago

OpenID Connect adapter for Jitsi Meet

Image
0

1.1K

galaxy102/jitsi-meet-oidc repository overview

⁠jitsi-meet-oidc

This application allows Jitsi to authenticate using OpenID Connect.

It is licensed under the MIT License. You can find the source code on GitHub: https://github.com/GaLaXy102/jitsi-meet-oidc⁠

⁠How to run

The normal use case would be to ship this application together with your Jitsi cluster behind a reverse proxy, for example with docker-jitsi-meet⁠.

You should set the following environment variables on the Jitsi containers (if you use the official builds):

JWT_APP_ID=jitsi-oidc # or another value
JWT_APP_SECRET=       # a random string of at least 32 chars
TOKEN_AUTH_URL=http://<HOST-OF-JITSI>:8080/.auth/authorize/{room} # Link to below service endpoint (best: configure it to run behind a reverse proxy on the same domain as your Jitsi with TLS)

You would then append your docker-jitsi-meet setup with the following service:

jitsi-oidc:
  image: galaxy102/jitsi-meet-oidc
  ports:
    - "8080:8080"
  environment:
    # Required:
    JITSI_BASE_URL:                   # URL to your Jitsi instance, e.g. https://meet.example.com
    JITSI_JWT_SECRET:                 # Same value as JWT_APP_SECRET
    JITSI_OIDC_REALM_URL:             # Path to your OpenID realm
    JITSI_OIDC_CLIENT_ID:             # OpenID client ID
    JITSI_OIDC_CLIENT_SECRET:         # OpenID client secret
    # Optional:
    JITSI_OIDC_BEHIND_PROXY:          # Set to "true" to trust X-Forwarded headers, needed behind reverse proxies
    JITSI_JWT_APPID: jitsi-oidc       # Same value as JWT_APP_ID, can be omitted when using the default
    JITSI_JWT_VALIDITY: 30            # Validity of emitted JWT in seconds -> Time until the redirect must have happened
    JITSI_OIDC_AVATAR_CLAIM: picture  # Claim containing link to user avatar in OpenID token
    JITSI_AUTH_BASE_PATH: /.auth/     # Base path of this application to allow running on the same URL as Jitsi behind reverse proxies

This config is insecure as it uses an unencrypted port to perform the OpenID flow, even though your identity provider should use TLS. Please see this only as an example and use a reverse proxy like Træfik Proxy⁠ to add TLS.

Tag summary

Content type

Image

Digest

sha256:299da3f41…

Size

26.2 MB

Last updated

about 4 years ago

docker pull galaxy102/jitsi-meet-oidc