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) Permit 1-factor Network Access to a Server 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
Cached (Offline) Workstation logon with YubiKeys Cached (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
2FA for File Shares 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 Troubleshooting
CLOSE

Replay settings for RDP and RDG 2008r2/2012r1

Some concrete examples:

  • RDP authentication: Place terminal servers or hosts that you must RDP to in the top list marked “These computers may initiate & share the window”.  If you need to RDP to DCs, also put "127.0.0.1" in the top list, because DCs authenticate to themselves over loopback.  Place your entire LAN IP range (or whatever subset will be initiating RDP connections) into the bottom list marked “these computers may only initiate the window”. 
  • RDP with RD Gateway (RDG): You would specify each server that will participate in the authentications together: the RDG server and all its possible terminal servers should share the same Replay window. Add them to the top "initiate & share" list. If clients are also coming from the LAN, then you should add the IP range of possible clients to the bottom "only initiate" list.

You can use groups or IP ranges rather than placing individual computer names into the lists directly. You can specify servers and IPs in more than one replay window if needed.

For an RDP/RDG scenario, a short window value of 20 seconds is probably long enough to allow all the authentications (RDG, RPC, Network Layer Authentication, remote desktop session) to complete. And after those initial connections, no more authentications need to be performed. If you are not able to connect, check your AuthLite Log on your DCs for recent replay events, and increase the associated replay window if needed.

Next Steps: