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

Using AD Connect Passthrough

Prerequisites

  • Link your directory to Office 365 with AD Connect, and configure Passthrough mode as shown here
  • Do not enable the passthrough "Single sign-on" option on AD Connect (it's not needed)
  • Using a non-AuthLite user, make sure you can log on with a synchronized user's UPN and password
  • AuthLite version 2.3.14 or later must be installed on your DCs and all AD Connect intstances (if you have any that are on member servers)

AuthLite Configuration

  • On each system running AD Connect, go into AuthLite Configuration -> Forced 2-factor Processes and add the process "AzureADConnect", click Apply

Testing

  • Your AuthLite users should be unable to log in with UPN and password now.
  • They should be able to log in by entering their normal password followed by a dash (minus) and their OTP, all together in the password field.  (For YubiKey, the dash character is optional)

Note that all primary Office 365 authentications for AuthLite users will now require 2-factor, including the login that happens when registering a new device for email access.  (Once registered, the device will no longer require user authentication each  time).