Easy to configure and use 2 Step Verification
Rating: 9 out of 10
IncentivizedUse Cases and Deployment Scope
We are using Google Authenticator for 2SV (Two Step Verification) for internal application login pages. This way, we are preventing any hacker throttling our applications and overloading it, thereby making it hard to use for real users. This is being used for our current client only for a particular system transformation project we are working on.
Google Authenticator uses TOTP (time-based OTP) and HOTP (HMAC based OTP) algorithms. The product is very reliable and easy to implement.
Google Authenticator uses TOTP (time-based OTP) and HOTP (HMAC based OTP) algorithms. The product is very reliable and easy to implement.
Pros
- Easy implementation: The product is very easy to implement both from embedding it into the application and from end users using it via their smartphones.
- You can use Google Authenticator to manage multiple two-factor authentication keys.
- Easy to add keys options: You can scan a QR code to set up 2FA in Google Authenticator. You can also do a manual entry using the unique key provided by the application you are setting up 2FA for.
Cons
- I once performed a factory reset of my smartphone which had Google Authenticator. I didn't have a backup for the device. When I restored my phone with the same google account, I was not able to restore the authenticator app settings. I had to add all the keys back into the app to use it. This is cumbersome, but I understand it is set up this way for security reasons.
- I don't like the ease with which it lets you delete a key. If I accidentally delete a key, I am doomed to get my 2FA key reset, unless I still have the QR code saved somewhere.
Likelihood to Recommend
Google Authenticator is cost effective and easy to configure. It is a reliable two-factor authentication device. It also lets you chose between TOTP and HOTP by turning on/off the time-based feature.