-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
allow specifying a register url in the server and redirect it from riot app #2257
Comments
This seems better reported at https://github.com/vector-im/riot-web |
But how all the apps will know sign up URL is different? Shouldn't synapse return the sign up URL so all clients will work? |
I think it will need a change in both synapse and clients. |
It is better to make user registration configurable like user authentication. if a registration provider is used in synapse config registration handler should use it. |
Any news on that? |
It is relevant to recently launched librem.one service as well (and any service which uses a common authentication system across multiple services), which uses a separate registration page and users cannot sign up using riot app. |
We have recently updated support for SAML2 and _some_support for LDAP. Adding more options for auth and registration is something we'd love to do, bandwidth is the only blocker. |
Though be mindful of #5130 |
With my changes in #5316 I have Riot showing me a button to login through my SAML2 SSO (Keycloak in my case). Though the PR is currently more or less just focused to get it working for my case of SAML2 SSO auth quickly. Means that on the login page of the SSO it could show as an extra link to signup, though I still see how an extra on the Riot web page already would be cool to have. |
I don't really understand what this issue is asking for. I think it's handled by the SSO login flow nowadays. In any case, I'm going to assume after over 3 years it's no longer particularly relevant and close it. |
Currently we have registrations directly from app disabled as we use diaspora accounts in diasp.in directly. Register url is https://diasp.in/users/sign_up
Similar is the case for disroot https://user.disroot.org/pwm-disroot/public/NewUser
It would be better if riot could redirect to the sign up url instead of we having to disable registration. It will be much cleaner experience overall.
The text was updated successfully, but these errors were encountered: