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) 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
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
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
CLOSE

Provisioning YubiKeys in Bulk / from Remote Workstations

YubiKey Programmer Operation Tab
YubiKey Programmer Operation Tab
Remove each key when it says "DONE". Don't click Finish until you're done programming *all* the YubiKeys
Remove each key when it says "DONE". Don't click Finish until you're done programming *all* the YubiKeys

If you do not have direct physical console access to your domain, or if you want to program a batch of keys efficiently in one sitting, then you can use the following process.

  • From AuthLite.com/downloads, install the "YubiKey Programmer" standalone program on your workstation.

  • Launch it from the Start Menu item called "AuthLite YubiKey Programmer"

  • Configure slot #1 for "AuthLite OTP" and slot #2 to "AuthLite Challenge/Response". More information on how AuthLite uses YubiKeys.

  • AuthLite ships YubiKeys with Smart card support Disabled. This is not mandatory for use, but can prevent Windows from being confused about the key when you plug it in each time.  You can use this screen to disable smart card support if you purchased your YubiKeys elsewhere.

  • If you are using shorter public IDs than the default, specify the number of bytes on this page as well.

  • Random public IDs can be used if you have a large number of ID bytes.  If you are using very short IDs, you should NOT randomly-generate them because you will end up with collisions (more than one key programmed with the same ID, which will cause an import error).

  • When ready, click “Start Programming”, and each time you plug in a YubiKey it will be programmed.

  • Remove the YubiKey when the status reads “DONE (remove key)”. Do not click “Finish” at this point, if you have more keys to program.

  • You can continue to plug in new keys and program them. When finished with all keys, click the “Finish” button.

  • Save the resulting XML file.

Note: This file should be considered sensitive information, as it contains all the secret values programmed into the keys. Treat this with the same security measures you would use for a password list or other secure document.

Next Steps: