Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User e-mail field for first login and password reset #5

Open
blaluc opened this issue Apr 8, 2020 · 2 comments
Open

User e-mail field for first login and password reset #5

blaluc opened this issue Apr 8, 2020 · 2 comments

Comments

@blaluc
Copy link

blaluc commented Apr 8, 2020

Hi,
I would need to pre-populate the server with a set of user that will be authorized to use the system.
Each user has a user-id, a display name and an e-mail address.
Is it possible, using matrix-corporal, to configure a policy whithout specifying the password (or specifying a random generated one) so as that at the first login the user can set a new password and confirm it by following the validation link received by e-mail? If not, which approach would you suggest?

Many thanks!

(the stack would includes ma1sd from your awesome ansible playbook...)

@spantaleev
Copy link
Member

Hi!

matrix-corporal can/will create users that it finds in the policy and assign a display name (and even a profile photo).

It can't currently manage email addresses for users though. Binding 3pids like email and phone numbers goes through some few other APIs and possibly depends on an identity server and manual confirmation of email/phone-number ownership.

I guess what we could do is, try to write to the user_threepids Postgres table (and possibly to user_threepid_id_server) directly. This is very Synapse specific, however. It also sounds a little dangerous. Doing it would require that matrix-corporal gets Postgres support first. As of now, we try to keep things fairly homeserver-independant -- while we do currently call into some Synapse-specific APIs, we never access the homeserver database.. I'm not sure messing with the database is something we'd like to do.

I think it's unfortunate that 3pids are separated like that and there's the whole Identity Server mess..

@KB1RD
Copy link
Contributor

KB1RD commented Aug 20, 2020

3pids can also be managed through the admin APIs, but that's also Synapse-specific.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants