-
Notifications
You must be signed in to change notification settings - Fork 9
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
Second authentication/confirmation to disable 2FA #214
Comments
Thanks for the report @stronenv, when you disabled 2FA was this shortly after it being enabled? |
Hi @pkevan! Yes, it was shortly after. I did disable it on another device, though, after logging out and back in again. |
Thanks for the extra details - we'll investigate further. |
@iandunn Do you think it makes sense if we implement the first suggestion |
That seems prudent 👍🏻 , but not necessarily high priority IMO, since it's easy to turn back on, and there are several status indicators to make it obvious when it's off.
🤔 We already have this in the revalidation process. It sounds like it maybe wasn't triggered in this case because of the time window where it's not required (ala If not, then that seems like it'd indicate a bug w/ the existing code that should be fixed instead. Maybe I missed something though? Possibly related WordPress/two-factor#578 |
Yes, I think this might be the case in the 2nd device, since the time window would start from log in. |
When disabling 2FA, you're not asked to confirm by entering a 2FA code, password, or asked to confirm.
Suggested improvements for disabling 2FA:
The text was updated successfully, but these errors were encountered: