feat(webauthn): support MFA-session passkey registration#47
Merged
Conversation
webauthn_registration_options/verify required a bearer token, unavailable during a token-withheld MFA offer. Add email/phone_number/ state so registerPasskey can authenticate via the MFA session cookie instead, and return the full AuthResponse (access_token on success) rather than a bare message. Also add mfa_gate to parseMfaRedirectParams so callers can tell an enrollment offer from a challenge for an already-configured factor.
This was referenced Jul 18, 2026
…fa_methods & mfa service-enabled fields
lakhansamani
added a commit
to authorizerdev/authorizer-react
that referenced
this pull request
Jul 20, 2026
) * feat(mfa): offer passkey enrollment during the login-time MFA setup AuthorizerMFASetup hardcoded passkey: false everywhere it was rendered with loginContext set (login/signup/OAuth/passkey-primary), and force-hid the option whenever loginContext was present at all - because webauthn_registration_options/verify required a bearer token that doesn't exist until the MFA gate is satisfied. The backend (authorizerdev/authorizer, authorizerdev/authorizer-js#47) now supports authenticating that ceremony via the MFA session cookie instead, so passkey is a real option here. Also, using the new mfaGate signal on the OAuth/magic-link return path: route to AuthorizerVerifyOtp for an already-configured factor instead of always showing the setup screen, and let AuthorizerPasskeyLogin's verify step render the same challenge form (previously told the user to sign in with a password instead). Removed a stale useEffect in AuthorizerVerifyOtp that flagged "Email or Phone Number is required" on mount even for the legitimate session-only resolution path these two flows now exercise. * feat(mfa): passkey login + MFA setup components, shared BackLink * chore(release): bump authorizer-js to 3.3.0-rc.2; v2.2.0-rc.1
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
1 participant
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.
Summary
webauthn_registration_options/webauthn_registration_verifycan now authenticate via the MFA session cookie (email/phone_number/state), not just a bearer token — needed so a passkey can be registered during a token-withheld MFA offer, before any token exists.webauthnRegistrationVerify/registerPasskeynow return the fullAuthTokenshape (access_token populated when this call completed the withheld MFA gate) instead of a bare message.parseMfaRedirectParamsgainsmfaGate: 'offer' | 'verify'so a host app can tell a first-time enrollment offer from a challenge for an already-configured factor.Backend counterpart: authorizerdev/authorizer#<branch feat/enforce-mfa-passkey-gate>.
Test plan
npx jest __test__/webauthnMethods.test.ts __test__/mfaRedirect.test.ts— all passing, new cases addednpm run build— cleannpx tsc --noEmit(consumer side, via authorizer-react) — clean