I have the same issue using MS Edge Extension! I thought something was wrong with the website i was on so I reset that website MFA but was failing to verify the code. Moving the code to the Google Authenticator App on the phone worked and showed that the codes generated do not match. The time on my Windows device is correctly set!
@mciantar Welcome to the forum!
So you don’t have an issue with TOTP autofill with the mobile app on iOS, but with the browser extensions on Windows?
To clarify, I don’t have an iPhone, only android phones and windows. I’m experiencing this issue on just one of my Windows Device’s browser extension. On other windows devices and on my android phone, the mfa code generation is working well.
Check the settings of browser extension to ensure Totp copy is on after an autofill.
@mciantar I just moved your issue into a separate topic, since both issues seem to be completely different. As I understand it @Gerardv514 experiences a change in the TOTP autofill process on iOS, while you @mciantar have an issue with the TOTP codes being invalid.
How do you know?
On your Windows machine, please create a new Login Item for testing purposes, and enter the following string in the “Authenticator Key” field:
otpauth://totp/TOTPgenerator?issuer=TOTPgenerator&secret=JBSWY3DPEHPK3PXP&digits=6&period=30&algorithm=SHA1
Next, open the following link in a web browser (on the same computer/browser as your Bitwarden browser extension):
Does the code generated by this website match what is generated by Bitwarden?
Nothing changed since my post explaining this issue. I have not restarted my device or the browser but now the Codes generated are back in sync with those show on my phone authenticator app (and also the test you described). Maybe it was a temporary issue?
Most likely your operating system synced the system clock (which it does periodically).
1 Like
A very handy web site. I’ve created a login using the TOTP Generator URL (no password; no username) and then entered the data into the Authenticator Key field.
While it has only happened occasionally, I have had a phone or PC with the wrong time.
1 Like