When SAML authentication is enabled in Synapse (saml2_config in homeserver.yaml) Riot clients no longer work for authentication.
Client will present an error message.
For Windows/Web client the message shown is:
Sorry, this homeserver is using a login which is not recognised (m.login.saml2)
For Android client the message shown is:
Log in with one of the following methods
Log in currently unavailable
For the web app:
For the desktop app:
For Mobile app:
Very interested in this feature. Due to it's lack SAML support of matrix synapse is currently useless.
Is there any progress regarding this issue?
SAML would be extremely helpful for a group of organizations I belong to
The SAML portion of this goes no where, since the reference ultimately points to OAUTH.
Any news on SAML authentication?
Does Riot Web currently support SAML2 or not?
Maybe @richvdh or @ara4n could shed some light on this?
@richvdh, @ara4n
Since SAML is only half implemented., ...
-1- Is there any (callback) function that can be called in a password provider to allow a custom SSO login when hitting the Riot Web index instead of SAML?
-2- Or is there any way to set the creds for Riot Web programmatically to establish a SSO, i.e. signing in the user in the backgound through the client-server API (https://matrix.org/docs/spec/client_server/r0.4.0.html#login) and handing over the creds to Riot Web (e.g. for function "Lifecycle.setLoggedIn([...})")?
As I understand it, SAML support is now fully implemented in Riot and Synapse... However, we'll still missing good docs on how to assemble everything together. We'll keep this issue open to track the docs work that remains.
see also https://github.com/matrix-org/synapse/issues/5764 on the docs front
SSO with SAML now works. And SSO can be used for UIA. But if both password auth and SAML are enabled in synapse, Riot will apparently prefer password auth, even if the current user has no password set: https://github.com/matrix-org/synapse/issues/5667#issuecomment-632035981
This should perhaps be consistent with login where if SSO and password are supported then Riot treats it as if only SSO existed.
it's mostly a misconfiguration if you're advertising both as it's expected that your SSO system handle passwords for you.
I'm actually going to close this as the docs front should be a separate issue, and likely fall mostly on the Synapse side.
Most helpful comment
SAML would be extremely helpful for a group of organizations I belong to