3 ms·
I think there’s a functional bug with very early (2006) accounts due to MFA or something. Good thing google has a high quality help desk to report bugs /s
by hsbauauvhabzb 3y ago
I think there’s a functional bug with very early (2006) accounts due to MFA or something.
Good thing google has a high quality help desk to report bugs /s
- londons_explore 3y agoI think if they have ever seen your account password in any password dump/leak (ie. if you reused the password elsewhere), then they effectively prevent password login. You have to have another already-active session. Makes sense really.
- sodality2 3y agoIt would make more sense to inform the user this, then enforce these checks until the user changes it. Anecdotally, my Google account's password has never been in any dump (password manager, very long random alphanumeric, changes every 6 months) and I too deal with these annoying prompts.
- hsbauauvhabzb 3y agoIn my case, the workflow requires a recovery token which was sent to an email account I have access to, authenticating with the token results in a security error. Despite having access to the password, the recovery email account and an active session, I could not activate a new session. It didn’t make sense, not that it matters when google refused to have a help desk or meaningful way to report bugs.
- _zoltan_ 3y agoWith Google One, you get support. And if you use storage from them you have google One.