Skip to main content

Step 7: Configure Google Authenticator

In previous step you retrieved and decrypted your Google Authenticator secret and OpenVPN profile.

In this step you will configure your authenticator app with the secret so you can generate the required codes for two-factor authentication.

Option A: CLI utility (oathtool)

If you are using iTerm2 then you can use built-in password manager to store your authenticator secret.

  1. Press option + command + F (or click Window > Password Manager) to open password manager
  2. Click + to add new password entry:
    • Name: OTP-non-live (or OTP-live)
    • Username: Your.Name
    • Password: Paste your authenticator secret here

  3. Install oathtool if not already installed:

      brew install oath-toolkit

  4. Paste following into your terminal to add handy alias to your .zshrc:

      echo '\nfunction oo() {
     echo -n "Enter the code:\\n"
     read -s code
     code=$(oathtool --base32 --totp $code)
     echo $code
     echo -n $code | pbcopy
  }\n' >> ~/.zshrc

  5. Close and open terminal or run exec zsh to reload your shell

  6. Run alias oo

  7. When prompted press option + command + F, select OTP-non-live and press enter

  8. Authenticator code will be generated and automatically copied to your clipboard

⚠️ You will have two separate authenticator secrets for non-live and live if you have access to both environments. So make sure to store each one as separate entries so you can easily retrieve the correct one.

Option B: Google Authenticator App

  1. Install Google Authenticator App on your mobile device
  2. Open the app
  3. Tap the plus (+) symbol in the bottom right
  4. Tap Enter a setup key
  5. Enter your email as account name
  6. Paste your Google Authenticator secret from the decrypted output into the Your key field
  7. Tap Add

Summary Checklist

✓ Authenticator setup in CLI or App

✓ Can generate authentication codes

Next step: Step 8: Configure VPN

← Back to onboarding overview

This page was last reviewed on 9 December 2025. It needs to be reviewed again on 9 June 2026 by the page owner platops-build-notices .
This page was set to be reviewed before 9 June 2026 by the page owner platops-build-notices. This might mean the content is out of date.