Re:Tell HN: Somebody implemented something I wrote a blog about
by rexfuzzle on Tuesday September 20, 2022 @10:10AM
(#32911868)
Interesting- I think that is the first time I've seen password and 2FA code on the same page. Guess that means you may not know if your password or 2FA code is incorrect depending on the error page
Re:Tell HN: Somebody implemented something I wrote a blog about
by soco on Tuesday September 20, 2022 @10:41AM
(#32912274)
Or the login process should just go ahead and ask the 2FA either way - and just fail you in the end without explaining why. And then notify only behind the scenes via mail that the password was correct but the 2fa wrong. That would be the way to handle it. I'd receive such notifications from time to time - I mix up the 2FA accounts sometimes, other times I'm slow typing and it expires - but I can live with that little extra email.
Re:Tell HN: Somebody implemented something I wrote a blog about
by Ayesh on Tuesday September 20, 2022 @11:16AM
(#32912863)
All my TOTP prompts (on websites I run) account for such delays and clock skews by checking against the previous and next TOTP. So even if the user is a little bit late to enter the OTP, I can still validate it and complete authentication.
Re:Tell HN: Somebody implemented something I wrote a blog about
by throwaway2037 on Tuesday September 20, 2022 @12:56PM
(#32914546)
This is standard practice with big corporate RSA remote login.
Customer support burden when the lose the 2FA key is solved by adding a hefty fee (around €100) to recover it. No webauthn support yet though.