-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trying to use E2ee module in jitis meet utilizing externally managed key handler but not found option to add external key #14704
Comments
Please, when you have questions or problems use the community forum before opening new issues, thank you. |
The external key needs to be set using the iframe API, it's not designed for direct user access. What problem did you have with the automatic key management? |
Here is an example of setting the key via iframe API and toggling e2ee in the meeting: jitsi-meet/doc/jaas/index-jaas.html Line 14 in 62d0d25
|
I follow the problem @VeshRaazThapa has reported. Specifically, it seems the |
Can you share the full piece of code of what you're trying to do? |
The app is running on local through
In
Nontheless the externallyManagedKey is undefined. |
I don't understand. You are configuring In addition, you can't just change config.js, since that file is served by the deployment. You should either have your own deployment or use the iframe API and use config overrides to change the settings you want. |
Ok I got it. Where can I find an example of iframe API? Or maybe another way for reading a config file. |
Check damencho's comment above. |
I've tried to include iframe api has below (in my custom component
However, this create a new instance of the conference which is not what I need. Is there an alternative to iframe api? |
Sorry, I have trouble understanding what exactly it is you are trying to do. How are you integrating Jitsi onto your app? Where does the external key come from? |
Sorry I'll try to be more clear. We are not integrating jitsi onto our app, our app is jitsi. We only want to customize the encryption key. Thus, we're modifing jitsi itself. What we want for now is the possibility to read from a confing file the |
Ok, it's clearer now! Then you'll want to enable the external key, yes, and then dispatch this action:
|
Yes but first thing we want to do at the starting of jitsi app is to read in some config file if |
The config is set to a global in |
Is it set to something in your config.js ? |
In config.js EDIT: |
I'm not sure what you mean by "deploy mode", but config.js is ONLY read when you deploy your code onto a server. It's not added to the JS bundle, it's included in the index.html by a server side include. |
@saghul we are following this guide https://community.jitsi.org/t/how-to-how-to-build-jitsi-meet-from-source-a-developers-guide/75422 |
DId you make sure to use correct root folder for your changes? Alternatively you can keep the config as is, and just override the modified files in /usr/share/jitsi-meet |
Issue: Setting Media Encryption Key and Activating Externally Managed Key Mechanism in Jitsi Meet
Description:
I've successfully activated end-to-end encryption (E2EE) in Jitsi Meet by toggling the option in the security settings. However, I encountered difficulties setting the media encryption key, which led me to hardcode my encryption key in
jitsi-meet/react/features/e2ee/middleware.ts
.To ensure the encryption key is properly set when participants join, I've dispatched the toggle button from code using
dispatch(toggleE2EE(false));
.Additionally, I tried activating the externally managed key mechanism by setting
externallyManagedKey: true
inconfig.js
. However, this didn't work as expected, and I had to modifyreducer.ts
to include the line:I'm seeking guidance on a better approach to set the media encryption key in Jitsi Meet when using an externally managed key handler. Also, I'd like to resolve the issue with activating the externally managed key mechanism.
Steps to Reproduce:
externallyManagedKey: true
inconfig.js
.reducer.ts
as mentioned to activate the mechanism.Expected Behavior:
externallyManagedKey: true
inconfig.js
.Server information:
Client information:
Additional information:
The text was updated successfully, but these errors were encountered: