Page MenuHomePhabricator

Configure subdomain to enable * Matrix user IDs
Closed, ResolvedPublic


To use Matrix IDs from a given domain, that domain needs to be authorized. We would like to use for the Foundation's internal Matrix deployment. Can you please set up to return the following JSON object:

{ "m.server": "" }

As discussed on IRC, we would prefer to use DNS if possible. I haven't heard back from the vendor on this yet, but I will update this task when I do.

Thanks for your help,

Event Timeline

Based on the Matrix docs and a recent blog post I believe the equivalent of that JSON object in their DNS format would be:

DNS 300    IN  SRV 10 5 443

I heard back from the vendor regarding DNS and the rep said "I have not found the DNS way for delegation in our internal docs, but also no explicit "we don't support it". So lets try it. The required DNS entry is described in the Spec under step 4 here:".

Let's also get rid of the old domain configuration added in T223835: Configure to enable * Matrix user IDs while we are at it.

(FWIW, a year ago I ran into some trouble with the DNS method, unfortunately I don't really remember the details - I think the modular admin panel checked for .well-known but not for the DNS entry?)

Change 623147 had a related patch set uploaded (by Gergő Tisza; owner: Gergő Tisza):
[operations/mediawiki-config@master] Revert "Add .well-known/matrix for"

Change 623348 had a related patch set uploaded (by CDanis; owner: CDanis):
[operations/dns@master] Add SRV record verification for Element Matrix Services

Change 623348 merged by CDanis:
[operations/dns@master] Add SRV record verification for Element Matrix Services

CDanis claimed this task.

Hey folks. Unfortunately, we discovered that the SRV/DNS solution is blocking our ability to use the Integrations feature on Element. The Integrations feature is what allows us to do self-service bridging configuration and other things. Can we use the URL for the well known file? Here is what the person from Element says:

"it looks like the SRV record setup for is incompatible with the integration setup. If at all possible, the quickest way to resolve this would be to have a well known file located at possible, because the integration manager will not work until then. You can use the bridges fine, but if you want to start playing with integrations we're going to need a well known setup. The SRV/DNS solution isn't really compatible. Sorry for misleading. If it's very difficult for you folks to set the well known up, we might be able to hack around it our side, but it's something we'd like to avoid as it's another thing to maintain in the stack."


Change 631529 had a related patch set uploaded (by Krinkle; owner: Krinkle):
[operations/mediawiki-config@master] docroot: add docroot

Change 631530 had a related patch set uploaded (by Krinkle; owner: Krinkle):
[operations/mediawiki-config@master] Add .well-known/matrix/server

Hey, sorry for the delay, we should be able to deploy this tomorrow.

Change 631529 merged by jenkins-bot:
[operations/mediawiki-config@master] docroot: expand docroot

Change 631530 merged by jenkins-bot:
[operations/mediawiki-config@master] Add .well-known/matrix/server

Mentioned in SAL (#wikimedia-operations) [2020-10-02T14:45:18Z] <cdanis@deploy1001> Synchronized docroot/ Separate docroot & add .well-known/matrix/server T261531 4573776bd 2fb4c20ae (duration: 01m 01s)

This is live now @bcampbell -- have Element give it a shot and let us know?