AuthLite Interactive Documentation
Home
Contents
CLOSE
AuthLite Interactive Documentation
Quick Start: Install and protect Domain Admins AuthLite Features Supported Tokens
How AuthLite uses YubiKeys
Installation and Upgrading
What platforms are supported? Prerequisites and Installation Linux systems MacOS machines
Configuration
Licensing AuthLite Set up User Groups
Configuring AuthLite to use your Group Pairs
Setting up the "Group for New Users"
Enforce 2-factor Logons
Use Group Policy to enforce 2-factor on Windows servers/workstations Secure Administrative Accounts with 2-factor Authentication Enforce 2-factor on File Shares using Access Control Lists (ACLs) Partial enforcement of a server (e.g. Exchange) with "Forced 2-factor Processes" Enforce non-Windows machines with "Forced 2-factor Computers" Enforce 2-factor logon to Office 365 with AuthLite LDAP logon support/enforcement
Windows Workstation (Endpoint) Protection
Offline Workstation logon with YubiKeys Offline Workstation logon with OATH tokens Zero-client two-factor workstation logons Workstation Safe mode operations
Remote Desktop
2FA over Remote Desktop Protocol 2FA with Remote Desktop Gateway / RemoteApp / RDWeb / RD Web Client
Replay Windows to support RDP and other re-authenticating protocols Replay Behavior setting VPN and RADIUS Configuration
Using IAS/NPS for RADIUS with AuthLite Microsoft VPN Client settings Wireless 802.1x Authentication DirectAccess and NetMotion Mobility XE Configure Watchguard SSL VPN with AuthLite
Active Directory Deployment Notes
Token Management
First: Configure Token Settings Provisioning Tokens Administratively
YubiKeys (Soft) OATH Tokens (Hardware) OATH Tokens OnlyKeys
User Self-Service
"Enroll in AuthLite" Windows program SET UP the Self-Service Web Portal USING the Self-Service Web Portal
View/Edit Existing Tokens Delegate Token Management Recovery Tokens Multiple OTP Tokens for the Same User Multiple users with the same OTP Token Password Operations
How to Log In
CLOSE

Supported Tokens

YubiKey v4/v5/FIPS
YubiKey v4/v5/FIPS
Google Authenticator and similar apps
Google Authenticator and similar apps
OnlyKey with firmware 2.1.1 or newer
OnlyKey with firmware 2.1.1 or newer

YubiKey

AuthLite uses the YubiKey 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.

YubiKey types

AuthLite supports any YubiKey with firmware v2.2 or higher, including the "Nano", and NEO.  AuthLite cannot use the blue “U2F Security Key” because it does not support OTP or challenge/response modes.

If you need NFC support, be sure to select YubiKey v5 tokens from the store. These are also called "YubiKey 5 NFC".


Soft Tokens (MS/Google Authenticator etc.)

AuthLite is also compatible with OATH Time-based One-time passcodes (TOTP) generated by smart-phone soft-token apps such as the free cross-platform Google Authenticator app or Microsoft Authenticator.  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.

OnlyKeys are programmed with a separate application.

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.

Next Steps: