Repository navigation
Sign in with a phone number (SMS code) as a first factor - #62
Merged
Merged
Conversation
NandanPrabhu
approved these changes
Nov 6, 2026
NandanPrabhu
previously approved these changes
Nov 6, 2026
NandanPrabhu
reviewed
Nov 6, 2026
pmathew92
reviewed
Nov 6, 2026
pmathew92
reviewed
Nov 6, 2026
pmathew92
reviewed
Nov 6, 2026
pmathew92
previously approved these changes
Nov 6, 2026
pacific-ring
force-pushed
the
feature/phone-first-factor
branch
from
November 6, 2026 10:25
2ab5e23 to
9920932
Compare
pacific-ring
dismissed stale reviews from pmathew92 and NandanPrabhu
November 6, 2026 10:33
The base branch was changed.
Email stays the first screen, as in the Figma. When the tenant also offers a phone, the email screen shows "OR" and "Continue with Phone", which opens a phone entry (country picker + number). Back goes code -> phone -> email. - LoginOption.PhoneOtp; IdentifyPhone and a texted/called VerifyOtp map to it - Repository.startOtp(method, identifier) replaces startEmailOtp; a phone is texted, or called when that is all the server offers for it - IDENTIFY_PHONE is now told to the server - State carries the method so Edit, Try again, Resend and MFA "Start over" return to the right screen; a submit from a screen that was just replaced and a switch while a code is being sent are dropped - CodeNotSent names the method; wrong-code text says phone - A phone or email the server refuses shows a full-screen "Invalid ... format" error (InvalidIdentifier); Try again keeps what was typed - Phone number is one E.164 string, at most 15 digits with the country code; the country starts as the United States, as in the design - Email and phone entry slide between each other (own transition key) - Country picker lists countries A to Z by name Co-Authored-By: Claude <noreply@anthropic.com>
…e device's - Keep the country picked for a phone number, so Edit and Try again show it again - Start the phone field on the device's country, falling back to the United States - Keep the server's rejection as the cause of an invalid identifier - Default the input field's leading content to an empty lambda - Correct the Back behaviour described for phone entry in EXAMPLES.md Co-Authored-By: Claude <noreply@anthropic.com>
pacific-ring
force-pushed
the
feature/phone-first-factor
branch
from
November 6, 2026 10:42
9920932 to
3d329ae
Compare
pmathew92
approved these changes
Nov 6, 2026
NandanPrabhu
approved these changes
Nov 6, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adding Support for Phone as an Option for first factor in embedded login
Type of Change
Testing
EmbeddedLoginRepositoryImplTest)Screenshots (if appropriate)
Phone_First_factor.mp4
Checklist
I have read the Auth0 general contribution guidelines
I have read the Auth0 Code of Conduct
All existing and new tests complete without errors