Duo at NCSA      

NCSA offers the Duo multi-factor authentication solution as a method of protecting and securing NCSA's resources.

Duo at NCSA accounts are available to all NCSA Kerberos account holders.

IMPORTANT: You must enroll with Duo using either a mobile app or a security key before attempting to log in. Keep reading below for details.

Prerequisites

Prior to beginning Duo enrollment for your NCSA account, take care of the following prerequisites.

  1. Know your NCSA Kerberos username and password.
  2. Install the Duo mobile app on your iOS/Android device or obtain a security key.

Enrollment Steps

With the above prerequisites satisfied, follow these steps to enroll using your iOS/Android device or security key.

  1. Visit https://duo.security.ncsa.illinois.edu in your web browser.
  2. Log in with your NCSA Kerberos username and password.
  3. Select Launch Device Management Portal.
  4. Follow the Duo process for enrollment. See https://guide.duo.com/enrollment for details.
  5. Generate and save 2 non-expiring one-time-use backup codes.
  6. (Optional) Add additional devices (phones, tablets, security keys).

FAQ

How do I use a backup code to recover access?

To use a backup code to add a new device/token:

How do I transfer my Duo setup to a new phone?

Can I use SMS as a Duo authentication method?

No, NCSA has disabled the SMS authentication method for our Duo deployment due to the security weaknesses of that method. See NIST is No Longer Recommending Two-Factor Authentication Using SMS for references on this topic.

My passcodes aren't working even though I'm pretty sure they should. What can I do?

If your passcodes have gotten out of sync with the Duo service, Duo supports the standard resynchronization algorithm which allows a user to provide multiple valid one time passcodes (OTPs) to get the remote server's counter back in sync with the local device. This is a secure method of resynchronization and does not pose a security risk because the OTP seed is not changed. Resynchronization may be needed because server's counter value is only incremented after a successful authentication where as the counter on the device is incremented with every request by the user. Because of this, the counter values on the server and on the token might be out of synchronization.

Where can I get additional help?

Send your questions, comments, suggestions, etc. to help+duo@ncsa.illinois.edu.

Corrections and suggestions for improvement to the above documentation are very welcome!