This site requires JavaScript to be enabled
An updated version of this article is available. You can only edit the latest version of the article
1389 views

12.0 - Updated on 2024-04-25 by Sara Grady

11.0 - Updated on 2024-03-28 by Amelia Brubaker

10.0 - Updated on 2022-04-11 by Denise Moser

9.0 - Updated on 2021-03-29 by Denise Moser

8.0 - Updated on 2021-02-23 by Denise Moser

7.0 - Updated on 2020-03-16 by Matthew McGuire

6.0 - Updated on 2019-10-29 by Ben Allen

5.0 - Updated on 2019-03-25 by Denise Moser

4.0 - Updated on 2019-03-18 by Denise Moser

Question

How do I setup Google Authenticator for Two Step?

Answer

  1. On your computer, visit okta.nd.edu
  2. Login with username and password
  3. If prompted for Two Step, respond with a previously enrolled device
  4. Click your name in the upper right corner
  5. Select Settings
  6. Locate the Extra Verification panel and the option for Google Authenticator Mobile App



  7. Click the Setup button beside it
    1. If you've previously configured the app and wish to reconfigure it, click Reset and then Setup
  8. Select the icon for the type of mobile device you have, then click Next



  9. On your mobile device:
    1. Visit your device's app store, then locate and install the Google Authenticator app (you may already have this installed for other services)
    2. Click on the add account, get started, or plus button, then choose Scan Barcode
    3. Allow camera access if prompted
    4. The camera will open, then scan the barcode (QR code) on your computer screen

    5. Enter your Touch ID if prompted
  10. Click Next
  11. Enter the code from your Google Authenticator app, then click Verify



  12. A message will appear confirming success. Click Done


Note: If you replace or upgrade the device that the Google Authenticator app. is installed on, the app. will cease to work.  For this reason, we recommend you enroll at least one additional option to be used as a backup, such as SMS (text message) or Voice Call. For information on other options please see KB0017212.