Software I Use: One Time Passwords

A one-time password (OTP) is a sequence of digits utilizing a cryptographic hash function to generate them. The numbers typically change every 60 seconds and are only valid during time, (although there can be a little leeway although probably only a few seconds worth). I use them mainly as part of a two-factor authentication (TFA) process for web sites and apps. That means when I log in to a web site, I will first provide my user name and password, but then it will require me to enter a valid OTP. This improves security as even if my base login credentials for the site were compromised, the attacker would also need access to my OTP, which is not as easily determined even if the attacker has access to a previously valid OTP.

I started using OTPs in 1998 as it was something my job had implemented for authentication to corporate systems. At that time, I was given a small physical device designed to fit on a key chain with an LCD display to show the numbers. Over time, OTPs became more and more prevalent on web sites as a way to increase security. Whenever they were offered, I tended to enable them, and today I have over 40 of them, (all are different). These days, some sites are offering something called Passkeys which are generally considered more secure, so I am switching to those as they are adopted. But I see having OTPs around for a while still.

I have used Microsoft Authenticator as a way to store all my OTPs and synchronize them across all my mobile devices for quite a while and have found it quite capable for what I do. However, in 2026, I started on a journey to move away from commercial cloud offerings and instead build my own personal cloud platform. An OTP is really designed to be on a separate device than your computer as part of the “something you know and something you have” idea behind two-factor authentication (TFA). So in the case of logging into a web site on my computer, my user name and password is the “thing I know”, and then an OTP device (in this case an app on my phone) is they “thing you have”. Of course, since phones are now used to access a wide variety of things, having an OTP manager on the same phone being used to log in somewhere reduces the security. Microsoft Authenticator allows you to require something like a fingerprint to unlock even if the phone itself is unlocked, which helps security but still is not strictly adhering to the idea behind TFA. However, I feel that OTPs, even if the client is on my phone, still offers a good layer of security to my accounts over just a user name and password.

While I have been fine with Microsoft Authenticator, in the spirit of moving things away from third-party providers, I started looking for alternatives. Honestly, this probably makes things less secure as my home network does not have teams of highly knowledgeable security folks watching over and managing things, but even though I am not sure what data Microsoft could mine from my OTP information, one of my goals is to keep my data fully under my control. Luckily, someone had created an OTP manager that integrated directly with Nextcloud, (the private cloud software I had chose to implement), called OTP Manager.

Installation of the software in Nextcloud and on my Android phone and tablet was easy and straight forward. The app did everything that I used Microsoft Authenticator to do, including needing a fingerprint to unlock, and in my view was more aesthetically pleasing. There was one major pain point, however, which was transferring all of my OTP data to it. There was no way I could find to “export” the data from Microsoft Authenticator then “import” it into OTP Manager. While some web sites and apps allowed you to add (and remove) OTP clients without totally re-doing things, there were only two or three of those. So, I had to log in to around 40 different sites, disable TFA for my account, then re-enable it and add the new OTP code to OTP Manager on my phone. This also synchronized things with Nextcloud so installing OTP Manager on my Android tablet was as simple as installing it and pointing it to my personal cloud. Once that was done, it automatically retrieved all my OTP data and made it available for use. If I ever decide to move to a different OTP client, it should be easier as Nextcloud makes the configuration data available in a plain-text format including the “seed” used. Even if the new client does not provide an easy import method, this should mean that I could add the existing OTP data manually without having to go through the process of disabling then re-enabling OTP on each site where it is used.

Honestly, I would not recommend self-hosting OTP data and instead keep it contained on a single device, (preferably with export and import functions that may be used if you change devices). Bonus points if your OTP client is only used to provide OTP data and not used to also browse the Internet and log into things. My migration from Microsoft Authenticator was more of an exercise in what could be done rather than making things more secure. Otherwise I would probably still be using it or comparable ones offered by Google and others, which in my view is much more secure if you use OTPs. I have already adopted the use of Passkeys as TFA for most of my “important” logins such as financial institutions, and will continue to move to Passkeys as more places provide the option. I also keep all my user name and password information in an encrypted “vault” which is managed outside of Nextcloud, so if someone gains access to one they will not automatically have access to the other.

In short: don’t do this; it is less secure than using offerings from the likes of Microsoft and Google. If you have any privacy concerns using their products, there are other “non-cloud” OTP options that you can run on a personal device. And for even greater security, use some sort of device that has no network or wireless connectivity, and is dedicated to only managing your OTP codes.