Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 72 Next »

This document is in progress!

Summary

Passwords alone are no longer sufficient. To address this RIT has moved to Duo's MFA service for the majority of services. Admins and developers, however, have access to large amounts of information and have privileges on servers that can cause significant damage if their credentials are compromised. Because of those risks, stronger and more efficient MFA is required for certain accounts. To achieve this, ITS has historically used OATH (One Time Passwords) for SSH and sudo access on Linux servers and recently started requiring either certificates + PIN or Duo for Windows logons.

OATH is deprecated and all OATH users are being moved to certificate-based authentication. ITS is issuing YubiKeys that will be used to securely generate and store these certificates.

Requirements

Considerations

  • These docs are not the only way to accomplish the goal nor are YubiKeys the only way to accomplish password-less authentication however the further you deviate from these docs the less knowledge ITS has to assist you.
  • The OS requires a lock on the YubiKey. If using multiple computers, even if a computer is virtual, multiple devices will be needed – one device per instance of the OS.
    • A YubiKey can be passed through RDP session(s) (Windows only)
  • Each device will have a different certificate. A certificate can, however, be used for access to both Linux and Windows servers.
  • Expert mode: While a YubiKey (i.e. a Yubico device) is not required, the docs and process are assuming a YubiKey is being used. Any device that can securely generate and store keys in a way that can be cryptographically verified will work.


Process Overview

  1. Initialize/Configure YubiKey
  2. Determine which certificate to use
  3. Submit certificate for verification
  4. Configure clients to use certificates
  5. Next steps

I. Initialize/Configure YubiKey

Unable to render {include} The included page could not be found.

II. Determine which certificate to use

The following is a suggested determination of which certificate process to follow. If you feel comfortable deviating, feel free to do so.


If you plan on utilizing your YubiKey to login into Windows workstations or Windows servers via RDP (from a Windows workstation) you need a Windows CA-issued certificated. Otherwise a self-signed certificate is sufficient.


 Windows CA-issued Certificate

Unable to render {include} The included page could not be found.


 Self-Signed Certificate

Unable to render {include} The included page could not be found.

III. Submit certificate for verification

 YubiKey Attestation and Submission

Unable to render {include} The included page could not be found.

IV. Configure clients to use certificates

Windows: YubiKey Windows SSH Client Configuration


Mac: YubiKey Mac SSH Client Configuration


Linux: YubiKey Linux SSH Client Configuration


V. Next steps

YubiKey Duo Setup - start.rit.edu/Duo

Other uses for certificates

Other uses of YubiKeys

Troubleshooting

  • No labels