-
Notifications
You must be signed in to change notification settings - Fork 120
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
2 Factor Authentication Ignored #20
Comments
Are you using livewire or inertia? |
Two factor is not working correctly on Livewire It should make the user enter the code to verify when enabling it |
I haven't taken a deep look at it yet but I think the problem is caused by the missing Add the below tag in your guest.blade.php head section and let me know if it does the trick.
|
Yes that solved that bug, but what about making them enter their code, before 2FA is actually enabled. To make sure their device is paired? Almost all websites do this As if they enable it and don't pair, they will be locked out of their account |
Found this issue Jetstream so maybe its a feature request? |
Ok, a new tag has been released to address this issue v2.1.4. Thanks |
Hi, I'm still not getting the 2fa screen after 2fa is enabled. I have the latest 2.1.5 update. I can see the app.js script is included within the guest.blade.php but once I enable 2fa and then try and login, it takes me straight to the dashboard without showing the 2fa screen. |
Yes, I am having the same issue with Laravel 9, PHP 8.1, jetstrap v2.5.4, jetstream v2.7.1 two_factor_confirmed_at just doesn't get written in the DB and stays null. |
Describe the bug
2 Factor Authentication is skipped completely
To Reproduce
Steps to reproduce the behavior:
Register an account in application
Proceed to Profile section
Enable 2 factor auth
Sign out
Log in again
Expected behavior
2 Factor Challenge should be prompted
Additional context
I did check all enabled features, updated the
I'm not familiar enough with the fortify to know whats happening.
The text was updated successfully, but these errors were encountered: