You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2024. It is now read-only.
Users may have multiple out-of-band proofs on a single account, in two dimensions. Users can have an email, a phone number, and an authenticator app. And, users can also have multiple of any of these factors – multiple email addresses, multiple phone numbers, and authenticator apps on multiple devices. In the case of say, multiple phones for SMS codes, we need to be able to let them pick which one to use. One option is to add a "display_name" to the "challenge type" to help the end user select which one to pick.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Scenario:
Users may have multiple out-of-band proofs on a single account, in two dimensions. Users can have an email, a phone number, and an authenticator app. And, users can also have multiple of any of these factors – multiple email addresses, multiple phone numbers, and authenticator apps on multiple devices. In the case of say, multiple phones for SMS codes, we need to be able to let them pick which one to use. One option is to add a "display_name" to the "challenge type" to help the end user select which one to pick.
The text was updated successfully, but these errors were encountered: