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

(Hardware) OATH Tokens

Prerequisites

  • AuthLite software installed on domain controllers and (if you are going to administer from a workstation) on that workstation machine.

  • Valid license or evaluation key entered.

  • A compatible OATH TOTP hardware token and its seed (secret) value.

Procedure

  • Launch AuthLite Configuration.

  • Select the item “Set up an OATH Token”:

  • The “Domain Name” box should contain the NETBIOS domain of the user account you wish to associate with this token. Since AuthLite only operates on the domain which it is installed, this should always be the current domain you are joined to.

  • In the “Username” box, enter the username (SAM account name, NOT UPN) of the user account you wish to associate with this token.

  • In Description/Serial, enter a unique ID for this key to distinguish it in data store.

  • Enter the seed from your OTP token's manufacturer. You can enter it in Hex, Base32, or Base64 format.

  • Specify an interval of 60 for Feitian/FTSafe tokens (c200). Some hardware tokens only change once per minute, instead of the normal interval of 30 seconds.  If you do not set this value correctly, your token will not work.

  • If this token is going to be used to log on to domain servers or online workstations, choose “Online authentication”. If you are defining an OATH token that will be used for offline workstations disconnected from the domain, choose “Offline”. A single OATH record cannot do both tasks, because the workstations must know the OATH secret for offline tokens, and this causes them to be less secure than the online tokens.

  • Select the Add to New Users Group checkbox and the user account will automatically be added to the AuthLite Users group.

  • Click the “Set up OATH Token” button.

  • If you are NOT using the “New Users” Group feature, then you must manually add this user into one of your AuthLite User Groups.

  • Make sure the proper user gets the token.

Note: The QR-code and other code readouts should be considered sensitive information, as they contain the shared secret used between the OATH token and AuthLite!