Latest 1Password Safari Extension Producing Incorrect One-Time Codes

I experienced this. It worked as soon as the code refreshed, but after 15 seconds or so, the site wouldn’t accept the code.

Hi both.

Most times we see errors with one-time passwords, it's because the system clock is slightly out of sync. Go to https://time.is/ and check if your system's clock is accurate.

It worked as soon as the code refreshed, but after 15 seconds or so, the site wouldn’t accept the code.

@chris55 This would suggest the system clock is ~15 seconds slow. After 15 seconds, the website will have ticked over to expecting the next code.

Slightly inaccurate clocks won't affect most things on your system – secure connections will still work, for example – but time-based one-time passwords require a higher degree of accuracy.

Let me know what you find out. :)

— Grey

I've seen this once before on my AWS account.

1. Make sure time is syncing with a time server.
2. Go to the vendor's website, remove TOTP, then re-add TOTP with a new secret.

Thank you for the suggestion! 🙂

-Dave

@Ryan_Parman , thanks for the suggestion. I think it's important to note that one should be careful about modifying the two-factor (one-time password rolling) codes when there's a mismatch in information between the apps/extensions. In other words, I thought my two-factor codes for a Google account somehow got screwed up in the 1Password app, as I had not made any changes for years, but I (accidentally) noticed the app & extension were showing different numbers. The point is one should be careful and have multiple two-factor methods when messing around with verification settings.

Update: I haven't noticed any issues with two-factor (codes) since updating to a slightly newer (but very beta) version of the apps/extensions. Fingers crossed!

Please let us know if you do run into the issue again in the future and we'll be happy to dig deeper.

-Dave

@nimvio: Sure. This has only happened to me once in the 10+ years I've been using 2FA.

@Ryan_Parman , I apologize but I left out the last part of my message (for what it’s worth). Basically, because of the one-time code glitch, I was going back and forth changing my two-factor settings on Google, and easily could’ve gotten the one-time settings mixed/messed up. Luckily, I had more than just the “rolling one-time code” method. You can almost imagine it’s like losing/misplacing a bitcoin… there’s no going back (if you’re not lucky).

I’m glad the issue hasn’t popped back up again, but I definitely experienced a problem.

Thank you for sharing. 🙂

-Dave