Element X status on EMS Cloud
This page outlines the current plan for making sliding sync (required for Element X) available for EMS cloud customers. The page will be updated if anything changes.
See the Element blog post “Element X: Ignition” for more information on Element X.
Hosts using traditional password authentication
All EMS hosts using traditional password authentication now have the sliding sync proxy and you can start using Element X.
If your host is using Custom DNS and you are not using “EMS hosts well-knowns”, you will need to update your client well-known file to enable Element X support. You will receive an email with specific instructions for your host. But, if you want to prepare, you can update your client well-known file like this:
GET https://yourcustomdoman.tld/.well-known/matrix/client
{
"m.homeserver": {
"base_url": "https://your-ems-hostname.ems.host"
},
"m.identity_server": {
"base_url": "https://vector.im"
},
"org.matrix.msc3575.proxy": {
"url": "https://your-ems-hostname.ems.host"
}
}
If you are not using Custom DNS or if you are using “EMS hosts well-knowns”, no changes are required by you.
Hosts using delegated authentication/SSO including Element One users
A pre-requisite of support for Element X is adding support for the Matrix Authentication Service (MAS) to Element Matrix Services (EMS).
Whilst significant progress has been made in developing MAS work to add support for it to EMS is not due until 2025 - we'd advise checking the Element Blog for the latest updates where we'll announce its support in the future.