Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
jitsi-meet/doc/jaas
damencho b9d5838398 feat(jaas-example): Uses conf-id generated from token generator. 2 years ago
..
8x8.vc-config.js feat: Jaas example that uses local jitsi-meet (#13350) 2 years ago
README.md feat: Jaas example that uses local jitsi-meet (#13350) 2 years ago
api_keys_kid.png feat: Jaas example that uses local jitsi-meet (#13350) 2 years ago
generated_key_dialog.png feat: Jaas example that uses local jitsi-meet (#13350) 2 years ago
index-jaas.html feat(jaas-example): Uses conf-id generated from token generator. 2 years ago
move-to-jaas.sh feat: Jaas example that uses local jitsi-meet (#13350) 2 years ago
nginx-jaas.conf feat(jaas-example): Uses conf-id generated from token generator. 2 years ago
update-asap-daily.sh feat: Jaas example that uses local jitsi-meet (#13350) 2 years ago

README.md

How to switch your deployment to JaaS in one easy step

Note: By default it will have e2ee(end-to-end) encryption enabled that works only on chromium based browsers (Chrome, Edge, ...). If a participant joins from another browser or mobile the e2ee is turned off.

In order to use your deployment with JaaS you first need to login to your JaaS Developer console and generate a key pair. Use Add API key button and then Generate API key pair. Make sure you download the generated private key from:

Make sure you transfer this downloaded private key to your server. Copy the key id from:

Now on your server run the helper script passing the private key file and the key id:

sudo /usr/share/jitsi-meet/scripts/move-to-jaas.sh /my/path/test-key.pk <key_id>

More information about JaaS Api keys at: https://developer.8x8.com/jaas/docs/jaas-console-api-keys

If you want to adjust the enabled services you can do that in /etc/jits/meet/jaas/nginx-jaas.conf. The part after proxy_set_body is the jwt token content that will be used for the client tokens. More info about the JaaS tokens: https://developer.8x8.com/jaas/docs/api-keys-jwt