Home
Contents
CLOSE
AuthLite Interactive Documentation
Quick Start: Install and protect Domain Admins AuthLite Features Supported Tokens Installation and Upgrading Configuration Token Management How to Log In Troubleshooting
CLOSE
YubiKey v5/FIPS
YubiKey v5/FIPS
Authenticator Apps
Authenticator Apps
OnlyKey with firmware 2.1.1 or newer
OnlyKey with firmware 2.1.1 or newer

YubiKey

AuthLite uses the YubiKey 5-series from Yubico Inc. as an inexpensive, robust one-time-code generating device.  YubiKeys have no display or battery, no moving parts, and are waterproof and virtually indestructible even in rugged environments.  They draw power from the USB port and are treated as an HID keyboard device so they work without special drivers on all platforms.

The YubiKey platform also contains extra cryptographic security features that allows AuthLite to securely authenticate users to offline (disconnected) domain workstations.

Yubico's Token Types

If you need NFC support, be sure to select YubiKeys that contain the word "NFC" in the product name.


Soft Tokens (Microsoft/Google Authenticator etc.)

AuthLite is also compatible with OATH Time-based One-time passcodes (TOTP) generated by smart-phone soft-token apps.  This is useful for cases where carrying a hardware token is undesirable or plugging in a USB device is impossible (such as authenticating to a 2-factor system from a smart phone).

Soft tokens cannot normally be used for logging into laptops that are offline from the LAN.  Please use YubiKeys for this use case.  There is a feature to create separate "Offline" OATH tokens, but the usability is challenging because the user must always know to choose the online or offline token by whether their computer can see the LAN.

OnlyKey

AuthLite version 2.4.2 and newer contain support for the OnlyKey  token running firmware 2.1.1 or newer.

Hardware OATH Tokens

Since AuthLite supports the OATH protocol for Time-based One-time passcodes (TOTP), it is also possible to use any hardware token that supports this protocol.  These tokens may only be used for "Online" logons, i.e. authentication to resources that can reach the LAN and the DCs.