-
Notifications
You must be signed in to change notification settings - Fork 325
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
fix(clerk-js): Handle two factor redirect when authenticate with web3 #5352
base: main
Are you sure you want to change the base?
fix(clerk-js): Handle two factor redirect when authenticate with web3 #5352
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
3902d48
to
091af83
Compare
🦋 Changeset detectedLatest commit: f57c9d1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
091af83
to
054d34e
Compare
factor-two
when authenticate with web3 and response status is needs_second_factor
…nd response status is `needs_second_factor`
054d34e
to
f57c9d1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to add an integration test for this? 🤔
}); | ||
switch (signInOrSignUp.status) { | ||
case 'needs_second_factor': | ||
await navigate('factor-two'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This assumes usage is always with in our components which is not the case.
Sounds like we need to borrow a few things from handleRedirectCallback.
Description
In this pr we're handling the redirect to
two-factor
when user try to login with web3 and has enabled theMulti-factor authentication
Checklist
pnpm test
runs as expected.pnpm build
runs as expected.Type of change
BEFORE
Screen.Recording.2025-03-18.at.11.19.54.AM.mov
AFTER
Screen.Recording.2025-03-18.at.11.18.31.AM.mov