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

AuthLite Features

Add Two-Factor Authentication to Active Directory

Unlike competing products, AuthLite integrates directly into the native authentication of Active Directory, allowing you to choose what users, systems, and processes will enforce 2-factor.  Virtually any authentication that backs to AD can be enhanced with 2-factor authentication.

At authentication time, a user supplies a One-time Passcode (OTP) in addition to their normal AD password.  AuthLite validates the OTP, and attaches a special group to the user's Kerberos session to identify that they logged in with two factors.  This allows all your systems and resources to check how the user logged on, and allow/deny access based on whether they used 2-factor (in addition to your existing checks for user group membership, etc).

Some examples of what AuthLite can do.

  • Secure Domain Admin accounts:  AuthLite can eliminate the "Pass the Hash" (PtH) attack vector against your administrative accounts, by limiting the privileges assigned to a user. When a logon is attempted without the OTP token, the user account will not have the Domain Admins group SID.
  • Secure endpoint workstation logons: With BitLocker and the AuthLite software installed, even offline (disconnected, cached credentials) access can be strongly secured with 2-factor authentication.
  • Secure network servers, file shares: AuthLite tags user sessions with different group SIDs depending on whether the authentication was done with 1 or 2 factors.  This enables you to define permissions on your file shares and network servers to precisely control what users may access them, and enforce 2-factor authentication exactly where you need it.
  • Remote Desktop: Require 2-factor access for certain users to reach Remote Desktop hosts (direct and through Remote Desktop Gateway). 
  • 2-factorize your VPN: AuthLite plugs in to Microsoft NPS RADIUS server, and can also be configured to enforce 2-factor for VPN servers that connect over LDAP.
  • OWA and Outlook Anywhere: Easily add 2-factor to your WAN email access.
  • Easy "pass-through": AuthLite uses the existing Username field (and in some cases the password field) to send its OTP to the server.  Since YubiKeys are HID keyboard devices, and soft tokens are just numbers you type in, you can always pass your credentials through remoting software, virtual machine interfaces, and all your normal workflows.  There's no need to worry about drivers or supporting weird protocols.  Virtually any authentication that backs to AD can be secured by AuthLite, with a minimum of infrastructure changes.
Next Steps: