Enable Google Authentication on Ubuntu

Install the Google PAM package

Google authentication relies on a Pluggable Authentication Module (a modular system that adds extra layers of security to the Linux login process) package.

Run the following command in your terminal to install the 💿 package:

sudo apt update
sudo apt install libpam-google-authenticator

Install the Google Authenticator app

The Google Authenticator app generates the secure one-time login codes you need for setting up Google authentication Ubuntu. Open the App Store on your iPhone or the Google Play Store on your Android device, search for Google Authenticator, and install the 💿 app on your phone before moving on to the next step.

On your mobile device, visit the app store and search for Google Authentication, or use this link:

https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2

After installing it on your mobile device, go back to Ubuntu and configure it to log in using a one-time password.

Configure Ubuntu

You configure Ubuntu for Google authentication Ubuntu by editing the system authentication file with a quick terminal command. This tells your system to check for the extra security code from your phone every time you log in, keeping your computer safe from unauthorized access.

sudo nano /etc/pam.d/common-auth

Then copy and paste the line below anywhere into the file and save.

auth required pam_google_authenticator.so

Paste the line anywhere in the file.

# since the modules above will each just jump aroundauth    required                        pam_permit.so
# and here are more per-package modules (the "Additional" block)
auth    optional                        pam_cap.so
# end of pam-auth-update config
auth required pam_google_authenticator.so

Save and exit the editor.

After that, run the commands below to initialize Google Authenticator.

 google-authenticator

Running this command triggers the setup wizard. You'll answer questions about your environment, and a QR code will appear in your terminal, along with some details below it.

Do you want authentication tokens to be time-based (y/n) y

Because terminal QR codes are notoriously tricky to scan with a phone camera, open the Google Authenticator app, choose the manual entry option, and type in the secret key shown on your screen.

Instead, open your mobile app and add a new profile, selecting the option to enter the setup key rather than scanning. Then, input the new secret key and the confirmation code:

Your new secret key is: M7I5532H5ZG4QYYEIQIMXFENIMI
Your verification code is 6593222
Your emergency scratch codes are:

Please take note and store it in a secure but accessible location.

In most environments, answering yes to all the questions will be enough to provide the kind of security that works.

Do you want me to update your "/home/richard/.google_authenticator" file? (y/n) y

Do you want to disallow multiple uses of the same authentication
token? This restricts you to one login about every 30s, but it increases
your chances to notice or even prevent man-in-the-middle attacks (y/n) y

By default, a new token is generated every 30 seconds by the mobile app.
In order to compensate for possible time-skew between the client and the server,
we allow an extra token before and after the current time. This allows for a
time skew of up to 30 seconds between authentication server and client. If you
experience problems with poor time synchronization, you can increase the window
from its default size of 3 permitted codes (one previous code, the current
code, the next code) to 17 permitted codes (the 8 previous codes, the current
code, and the 8 next codes). This will permit for a time skew of up to 4 minutes
between client and server.
Do you want to do so? (y/n) n

If the computer that you are logging into isn't hardened against brute-force
login attempts, you can enable rate-limiting for the authentication module.
By default, this limits attackers to no more than 3 login attempts every 30s.
Do you want to enable rate-limiting? (y/n) y

As you'll see, you'll still need to verify your username and password, but a third layer, a one-time code, will also be required to log in.

Enter the code from your mobile device to complete the verification.

This completes the setup.

If this didn't work: Verify that you copied the secret key correctly into the authenticator app and that your system time is synchronized.