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

Use Group Policy to enforce 2-factor on Windows servers/workstations

Fig. 1) AuthLite Users and Policy Venn diagram
Fig. 1) AuthLite Users and Policy Venn diagram
Fig. 2) User Rights Assignment Allow/Denies
Fig. 2) User Rights Assignment Allow/Denies
Fig. 3) Authlite Groups and Policy
Fig. 3) Authlite Groups and Policy

The most flexible way to enforce 2-factor authentication is to use Windows' built-in security controls. Our User Group Pairs feature means that you can set up group policies and ACLs that are aware of AuthLite Users and whether they logged in with two factors.

Important: The following is one of the most critical concepts to understand in AuthLite

In order to be Enforced as 2-factor, a user must be both an AuthLite User and requesting access to a computer or resource that has been told to enforce 2-factor for AuthLite Users.  See (Fig. 1) for an illustration.  This has important implications:

  • Simply being an AuthLite User alone is not enough to "enforce" anything.  You also have to tell the resources that they should be enforcing 2-factor for AuthLite Users.  And conversely:
  • Simply telling a resource to enforce 2-factor for AuthLite Users will not block other, non-AuthLite Users from authenticating.  This is very important to understand.  You still can block whatever users and groups that you want, but you just use your existing group policy and ACL controls to do that; it has nothing to do with AuthLite.

AuthLite does not replace existing permission controls (AuthLite does not try to block non-AuthLite users).  AuthLite just adds one more "check": if you're an AuthLite user and you are logging onto something that blocks access from 1-factor AuthLite users then enforcement occurs.

You can use Group Policy to restrict how AuthLite Users are allowed to authenticate to certain machines, by setting the "Allow" (green highlight) and "Deny" (red highlight) sections in "User Rights Assignment", as shown in Fig. 2.  Please refer to the video for a walkthrough of this feature.

Note: Make sure to test that 1-factor authentication is blocked as you expect.  It is possible in AuthLite to have 2-factor working but without properly enforcing 1-factor yet.

Next Steps: