MFA provider "google" is really "totp"

[delroth]

The MFA provider currently called "google" is just a TOTP implementation and doesn't have anything specifically to do with Google Authenticator. I use a different TOTP wallet app on my phone and haven't noticed any problem with it.

How about having "totp" as the canonical name for this provider and "google" as an alias? This would make it clearer what this provider actually works with.

[Luzifer]

Indeed as it's currently built it is a TOTP provider using quite specific settings which are used by the Google Authenticator. TOTP allows 6 or 8 digits and different rotation times.

Also "Google Authenticator" is a quite common term used for these TOTP implementation. In my experience not many people are aware of the existence of the TOTP authentication mechanism but most are aware of the "Google Authenticator".

About the app usage: Sure, you can use every app / service you like as soon as they support the settings mentioned above: Authy, LastPass, Vault-TOTP, …

Regarding the name change: I think this should go along with adding more configuration options for the TOTP provider. For backwards compatibility the provider must also listen to the google provider id.

[Luzifer]

The fully configurable TOTP provider is implemented into master and will soon be released. The default is now to use totp as a name and google acts as a backwards compatible fallback.