Replies: 1 comment
-
|
We've implemented registration tokens a few months ago, it's the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am setting up a Synapse homeserver for my friends.
I want invited users (potentially casual, mobile-only users) to register on my homeserver. This requires a registration flow that is simple for users (and preferably for me too!) but also prevents unauthorised registration.
MSC3231 (Token Authenticated Registration) seemed to be the best mechanism for this, but I understand that this is not implemented in MAS.
I assume I would be encouraging mobile-only users to use Element X (and in any case, token-authenticated registration is not implemented in Element).
As MAS is required for registration through Element X, this means I cannot use token-authenticated registration with mobile-only users.
Looking at the docs, one workaround I identified would be to ask a new user their preferred username before registration, add it to the
allowed_usernames.literalsfield of the policy settings in MAS, and presumably restart MAS to reload the config. This would allow restricted registration that is relatively simple from the user perspective, but it is not a very elegant workaround.So my questions:
Beta Was this translation helpful? Give feedback.
All reactions