#2209 Google Authenticator support

[Shift4SMS]

This is really a two-part request. The first is to natively support Google Authenticator for opening up a .kdbx database. This would require the user to have a Google Authenticator app available and previously synced with the database.

The second is to include the ability for KeePass to act as a Google Authenticator - similar in capability to what WinAuth does: https://winauth.com/download/. This is another open-source application. Initially I see the password field of an entry being dynamic, long-term maybe tracking username, password and authenticode as individual fields (right-click copy password, right-click copy authenticode,,,) - although I'm not sure if or how right-click perform auto-type would work (username & password is the same but authenticode is often a pop-up).

[wellread1]

The first is to natively support Google Authenticator for opening up a .kdbx database. This would require the user to have a Google Authenticator app available and previously synced with the database.

Currently, KeePass databases can be opened using Google Authenticator to generate HMAC-OTPs. This plugin does not support the time based variant, i.e. TOTPs. Due to the way KeePass works, a minimum of three OTPs are needed to open a KeePass password database.

The popular time based OTPs (TOTPs) can not be used to open a KeePass database. Due to the way KeePass works, support for TOTPs is unlikely.

The second is to include the ability for KeePass to act as a Google Authenticator -

Like Google Authenticator, KeePass can natively generate counter base OTPs using the built-in {HMACOTP} placeholder. There are also two plugins that add TOTP generators like Google Authenticator. See KeeOTP or Tray Top.

[Shift4SMS]

Thanks. Actually I ordered the request wrong, I was mostly interested in the second part but you answered both.

I've never used plug-ins for KeePass. It sounds like KeeOTP will do what I'm asking. Thanks again.