Warning |
---|
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 YubKeys that will be used to securely generate and store these certificates.
Requirements
- YubiKey 4.3 or later (Typically this is a YubiKey 4 or newer)
- Latest version of OS
- Yubikey Manager
Considerations
- These docs are not the only way to accomplish the goal nor are YubiKeys required 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)
- 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 built 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
- Initialize/Configure Yubikey
- Which Certificate Is Right For Me?
- Generate certificate
- Submit certificate for verification
- Configure clients to use certificates
Expand |
---|
title | First steps with Yubikey |
---|
|
Include Page |
---|
| Yubikey New Setup/Initialization/Re-initialization (WIP) |
---|
| Yubikey New Setup/Initialization/Re-initialization (WIP) |
---|
|
|
Note |
---|
The following is a suggested determination of which certificate process to follow. If you feel comfortable deviating, feel free to do so. |
If you primarily log into and work mainly with Windows machines, please follow the process below:
Expand |
---|
title | Windows CA issued Certificate |
---|
|
Include Page |
---|
| Yubikey Smartcard Setup via Windows CA-issued Certificate (Yubikey Manager) |
---|
| Yubikey Smartcard Setup via Windows CA-issued Certificate (Yubikey Manager) |
---|
|
|
Else, follow this process below:
Expand |
---|
title | Self-Signed Certificate |
---|
|
Include Page |
---|
| Yubikey Smartcard Setup via Self-Signed Certificate (Yubikey Manager) |
---|
| Yubikey Smartcard Setup via Self-Signed Certificate (Yubikey Manager) |
---|
|
|
Submit certificate for verification
Expand |
---|
title | Yubikey Attestation and Submission |
---|
|
Include Page |
---|
| Yubikey Attestation |
---|
| Yubikey Attestation |
---|
|
|
Other uses of Yubikeys
==OLD==
Generating and distributing(?) certificates
Windows
Enroll certificates using the following Guide:
Configure Windows to automatically load certificates from the Yubikey for SSH use:
macOS
Note |
---|
If you plan on using your certificate with Windows and linux servers, you must generate the certificate using Windows. Once the certificate has been generated on Windows it can be used with any OS and with Windows and linux servers. |
Linux
Note |
---|
If you plan on using your certificate with Windows and linux servers, you must generate the certificate using Windows. Once the certificate has been generated on Windows it can be used with any OS and with Windows and linux servers. |
Using certificates