Element X, Call and Server Suite are production ready

[humptydumpty]

I wonder what this means for our self hosted instances.

[infogulch]

From this release of ESS (24.09) onwards our server (Synapse) will come with [Server-side synchronisation] SSS as standard.

The latest version of synapse 1.115.0 is already packaged and available, and CHANGES.md has a lot of mentions of the Sliding Sync API, so maybe it just works now.

There's also Element Server Suite (ESS) which looks like an "enterprise ready" packaging of synapse and related components for kubernetes. Not sure how this relates to cloudron deployments. Introduction to Element Server Suite

[girish]

There is a discussion here - https://github.com/matrix-org/sliding-sync/issues/461 whether the proxy is still needed.

The release notes of https://github.com/element-hq/synapse/releases/tag/v1.114.0 says "This release enables support for MSC4186 — Simplified Sliding Sync. This allows using the upcoming releases of the Element X mobile apps without having to run a Sliding Sync Proxy." . So , I guess the proxy is not needed anymore.

[girish]

I tested out Element X now... but unfortunately can't even login. After much searching, it looks like the app doesn't support OIDC yet. This is tracked in https://github.com/element-hq/element-meta/issues/1915

[girish]

Can confirm the Element X app works without OIDC auth.

[andreasdueren]

@girish said in Element X, Call and Server Suite are production ready:

Can confirm the Element X app works without OIDC auth.

Have you put this documentation into consideration?

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"
    }
}

[girish]

@andreasdueren That doc was last updated 7 months ago, so I am guessing it is updated. My understanding is that the standalone proxy is not needed anymore. The org.matrix.msc3575.proxy is also not needed anymore since the sliding window is part of synapse. I could be wrong though.

[andreasdueren]

@girish Sorry don't know why I wrote that. You're right, looks like msc3575 is not needed anymore.

[andreasdueren]

Looks like this Issue issue gives a hint as to why SSO is not working

Element X only supports native OIDC or password login and not the old m.login.sso flows

How is SSO currently implemented?

[girish]

@andreasdueren yes exactly, that's the bug. They are yet to add OIDC support in the Element X apps . the one you linked is the iOS app, the one I linked earlier was for the android app.

[andreasdueren]

This post is deleted!