Update customers.gitlab.com to allow for phone and email combination to authenticate a user
Problem
As a user, I should never know that gitlab.com uses a separate application to manage my subscriptions. As a result, I should not have to create an additional username and password in order to manage my account. If GitLab uses a separate application, I should be able to manage any options within that application with the information that I have already provided GitLab.
As a result, we need to update customers.gitlab.com in order to let a user generate an authentication token with a passcode sent to the users mobile number, or email as a backup.
Prototype
User enters their email address
GitLab looks up if the user should authenticate via password or via mobile / email code
If the user should authenticate via password, let them auth via password
If the user should authenticate via mobile / email code let them auth via mobile / email code
Requirements
- Initially requires only email
- Includes a loading state when querying if the user should authenticate via password or code
- Requires password when the user should authenticate via password
- Requires code when the user should authenticate via authentication code
- Allows the user to send their authentication code via email (instead of text)
- Sends branded email to the address the use entered with authentication code
- Loads contextualized error when authentication code is incorrect
- Includes a loading state when attempting to authenticate the user
- Pushed user to https://customers.gitlab.com/plans on authentication
Relates to
The above issue relates to product#87 (closed)