element-hq / element-hq/element-integration-manager
Manually creating a Jitsi widget ignores the domain set within the config preferred_domain
- Dominant language
- No language data
- Stars
- 11
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
When using the default element integration manager, its not possible to add a jitsi-widget/extension manually that actually points to the jitsi server set in the config or well-known. It always uses `meet.element.io` instead of the actually preferred one
**To Reproduce**
Steps to reproduce the behavior:
1. use the default element config settings for the integration manager:
```JSON
"integrations_ui_url": "https://scalar.vector.im/",
"integrations_rest_url": "https://scalar.vector.im/api",
"integrations_widgets_urls": [
"https://scalar.vector.im/_matrix/integrations/v1",
"https://scalar.vector.im/api",
"https://scalar-staging.vector.im/_matrix/integrations/v1",
"https://scalar-staging.vector.im/api",
"https://scalar-staging.riot.im/scalar/api"
],
```
2. Configure your jitsi preferred_domain according to the docs: https://github.com/element-hq/element-web/blob/develop/docs/config.md#voip--jitsi-calls
I have the config set in my .well-known/matrix/client:
```JSON
{
"im.vector.riot.jitsi": {
"preferred_domain": "jitsi.domain.net"
},
"jitsi": {
"preferred_domain": "jitsi.domain.net"
},
```
where I tried both settings.
I also tried using the settings regarding the element-config.json:
```JSON
"im.vector.riot.jitsi": {
"preferred_domain": "jitsi.domain.net"
},
"jitsi": {
"preferred_domain": "jitsi.domain.net"
}
```
4. Click on Extensions > Add Extensions > Jitsi Meet > Add
6. Check out the created widget (open in new frame to see the URL it used)
7. See that `meet.element.io` is used instead of the actually preferred_domain
**Expected behavior**
Use the preferred_domain used in the config and/or well_known/matrix/client
**Client (please complete the following information):**
- Matrix Client and Version: Element-Web
- Matrix Client Version: 1.11.85
- Browser: Firefox, Chrome
**Additional context**
I also tried snakeCase instead of camel_case since I read about a bug where only the old snakeCase actually worked but to no avail.
The only solution to this I could think about was using the completely deprecated integration manager called dimension but this would incur heavy security risks
Is there an (undocumented) setting with the `integrations_widgets_urls` config settings where I can make element point to the correct jitsi domain?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.