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

Only let in 2-factor users, block all others

Fig. 1) User Rights Assignment Allow/Denies
Fig. 1) User Rights Assignment Allow/Denies

If you want to allow ONLY 2-factor users on a particular machine, just break the problem into two parts:

  1. Use group policy to constrain the set of users who are allowed to log on, to only "AuthLite Users".  Do this using the Computer policy's "User Rights Assignment" sections highlighted in Green.  Anyone not represented in these settings will not be allowed.
  2. Now, add "AuthLite 1F Tag" to the sections highlighted in Red.  This adds the additional constraint that even if you would otherwise be allowed to log on, 1-factor AuthLite users are blocked.

As a quick example, if you set the "Allows" to "AuthLite Users" (or you could choose "AuthLite 2F Tag" here), and then set the "Denies" to "AuthLite 1F Tag", then you have successfully blocked everyone but 2-factor AuthLite users.  This may not be what you truly want; consider that you should still allow "Administrators" to log on too.  (That will cover local admins as well as all domain admins).

Note: Always test that 1-factor logons and authentication of disallowed users gets blocked properly as you expect.  Just because 2-factor is working does not imply it is being enforced successfully.