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

USING the Self-Service Web Portal

Enter Username
Enter Username
New user: enter password
New user: enter password
Select to add a YubiKey or OATH token
Select to add a YubiKey or OATH token

Prerequisites

  • First, Set up the self-service provisioning portal web application
  • Program and Import your YubiKeys (unless you only want to use OATH tokens)
  • Distribute your programmed and imported (but still unassigned) YubiKeys out to your users

First Portal Login

  • Each user browses to the Intranet URL of your provisioning portal

  • Enter the username and hit Submit

  • If this user is not in any AuthLite Group yet, they are now asked for their password

Adding a YubiKey

  • After logging in to the portal, select "Add YubiKey"
  • Plug in the YubiKey to a USB port
  • In the YubiKey Passcode field and touch the YubiKey button to enter an OTP from this key.

  • Click “Add” and then the YubiKey will automatically be associated with this user account, and the user will be added to the “New Users” Group

Adding an OATH Token

  • After logging in to the portal, select "Add OATH Token"
  • If this token is going to be used to log on to domain servers or online workstations, choose “Online”. 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.)

  • Click “Add” and then a QR code will be displayed. The user can snap this with the Google Authenticator app on their phone, and then click “Done”. The new OATH token will automatically be associated with this user account, and the user will be added to the “New Users” Group.

Logging in later to manage tokens

  • After enrolling in AuthLite, the user can also log in to this portal again to add/manage their tokens.
  • Since they are already AuthLite users with at least one token, they must supply their password and an OTP token to gain access.  (This prevents an attacker with knowledge of the password from using this portal to "bypass" 2-factor restrictions by minting new tokens for the user.)

Troubleshooting tasks: