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
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
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
Administer tokens
CONFIGURE Token Settings dialog SET UP New Tokens
Provisioning Tokens Administratively
YUBIKEYS: Provisioning Administratively (Soft) OATH Tokens: Set up Administratively (Hardware) OATH Token Provisioning
Self-Service Provisioning
SET UP the Self-Service Web Portal USING the Self-Service Web Portal
MANAGE Existing Tokens DELEGATE Rights to Manage Tokens RECOVERY Tokens Multiple OTP Tokens for the Same User Multiple users with the same OTP Token Password Operations
How to Log In Event Logging
CLOSE

Enforce non-Windows machines with "Forced 2-factor Computers"

Fig. 1) Forced 2-factor Computers dialog
Fig. 1) Forced 2-factor Computers dialog
Fig. 2) Computer name tracking dialog
Fig. 2) Computer name tracking dialog

You can tell domain controllers to reject one-factor authentication from AuthLite users if the requests originate from certain machines.  This is not as robust or granular as using group policy and access control lists, but is still be useful for some circumstances.  For example, non-Windows machines (such as MacOS, Linux, etc.) don't honor group policy, so they must be forced by this dialog (see Fig. 1).

By default, settings will apply equally to all AuthLite user groups.  You can select a specific group from the dropdown and create settings that will apply only to that group.  Each group can have its own settings applied, in addition to the settings that apply to all groups.

Select by IP Address / Range

  • Enter one or more IP ranges into the Forced 2-Factor Computers list. 
  • Any time an AuthLite user authenticates from a computer represented in this list, the domain controllers will require two-factor authentication before allowing the authentication.

Security Note: If any of your domain controllers in the site are missing the AuthLite software, then they will not enforce or understand two-factor authentications.

Selecting by Name/Group

It is possible to select machines and security groups by name.  AuthLite will try to decide what machine is connecting by keeping a map of IP addresses to computer names (see next section).  It is not always possible to determine the computer name accurately, so you should use the IP Address selection instead wherever possible.

Computer Name Tracking

If you are enforcing 2-factor computers based on computer names or groups, it is highly recommended to activate Computer Name Tracking (see Fig. 2).  This will help AuthLite software on the DC's to associate incoming authentication attempts with the correct domain member machine, and prevent spoofing the identity of client systems for the purpose of bypassing two-factor restrictions.

Next Steps: