So as long as you have an authenticator which can do longer passwords than 6 characters and do custom time periods, then congratulations, you can use the following method.

Authy's secret keys are in hex already, so they need to be turned back to base32 for working QR codes.

Don't substitute this period longer in your Authenticator. Authy shows 20 seconds, but that means a slightly different thing.

The password validity period is 10 seconds (instead of usual 30).

The passwords are one digit longer - 7 digits (usually they're 6, with exceptions), but if you've looked at one of the Authy generated passwords already, you probably noticed it too.

They use the exact same algorithm to generate passwords as Google Authenticator and similar (TOTP).I had to adapt the code a little and you can see the result below, but here's what I discovered about Authy's method: My guess is that Brian used the code to extract the keys that weren't necessarily tied to Authy.

But when I tried that code, nothing appeared on the screen. If this was not possible, I guess people would be reverse engineering the Android app or something like that. His method is to extract the secret keys using Authy's Google Chrome app via Developer Tools.

His post had a neat code with it to generate QR codes for you to use on your favorite authenticator. I couldn't find any completely working solutions, however I stumbled upon a gist by Brian Hartvigsen. Since I use 1Password for all of my password storing/generating needs, I was looking for a solution to use Authy passwords on that. However many users who aren't using Authy, have their own authenticator setup up already and do not wish to use two applications for generating passwords. There is an increasing count of applications which use Authy for two-factor authentication. Generating Authy passwords on other authenticators

Bitwarden totp