The average time drift for TOTP hardware tokens may be up to 2 minutes per year...
After a period of time (i.e. 1–2 years) some of the tokens may drift outside of the global synchronization window. A token that is
not used very often is likely to drift even more beyond the synchronization window that an authentication server is using. In addition, organizations are afraid to keep a large stock of hardware tokens: a token that is not used at all will have its battery almost like new, but the time-drift will not allow
using the token at all, which causes such investments to be completely unprotected.
To address this issue, we have developed products that allow syncing the hardware clock using a special app: miniOTP-2 and OTPC-P1. The application is planned to be published on the Google Play soon.
TOKEN2 NFC Burner 2 Android application
These products are not ready to be shipped yet, but we are expecting the stocks to arrive in February 2019. miniOTP-2 can be pre-ordered here.
New programmable hardware tokens with time sync feature
31-01-2019Yet another review of OATH hardware tokens feature in Azure Cloud MFA
22-01-2019Programmable TOTP token in a key fob form-factor
12-01-2019TOKEN2 NFC Burner Windows application
07-01-2019Introducing world's first programmable TOTP tokens with time sync
03-12-2018Token2 TOTP Toolset
14-11-2018New product: OTPC-N1 - OTP Display card
30-10-2018New product: Token2 TC201 hardware token
26-10-2018Token2 C101 token WebUntis compatibility
23-10-2018Microsoft Azure Cloud MFA OATH hardware tokens support (public preview)
27-09-2018Which Token2 hardware token is right for my Azure MFA?
25-09-2018Enable hardware token based two factor authentication for Meraki Dashboard account
23-09-2018Enable hardware token based two factor authentication for your Stripe account