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

wire up MSISDNs as 3PIDs #1903

Closed
matrixbot opened this issue Jul 30, 2016 · 2 comments
Closed

wire up MSISDNs as 3PIDs #1903

matrixbot opened this issue Jul 30, 2016 · 2 comments

Comments

@matrixbot
Copy link

Created by @ matthew:matrix.org.

@ara4n
Copy link
Member

ara4n commented Dec 20, 2016

In practice, this means:

  • Make sydent able to validate MSISDNs for maintaining a MSISDN->MXID mapping for discovery purposes
  • Make synapse able to track the resulting verified MSISDN 3PID as associated with an account (as we're not doing the split-out yet)
  • Make riot able to register you with either MSISDN, email, or neither.
    • We don't need to do the dance that Blah did to mandate email address to protect against MSISDN reuse, as we mandate the password (or perhaps in future some other login flow) to check the user's identity.
  • Make riot do an IS verification dance for MSISDNs just as it does for email addresses.
  • Make riot show MSISDN 3PIDs in UserSettings sensibly
  • Make riot show and manage the MSISDN associated with your account in UserSettings sensibly
  • We do not get sucked into doing 2FA a la 2FA for logins element-meta#345.

@dbkr
Copy link
Member

dbkr commented Mar 16, 2017

This should all be done now!

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

No branches or pull requests

4 participants