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 AD Federation Service (ADFS)

Prerequisites

  • Link your directory to Office 365 with AD Connect, and turn on AD FS federation (using the AD Connect tool or powershell commands)
  • Do not enable the "Single sign-on" option on AD Connect (it's not needed with modern authentication)
  • In the "Edit Authentication Methods" ADFS dialog, please select "Forms" and de-select "Windows authentication". This will make sure apps on the intranet use Modern authentication (which can call the ADFS form web page, which supports AuthLite logon)
  • Using a non-AuthLite user, make sure you can log on to Office 365 with a synchronized user's UPN and password, and that you're seeing the ADFS web form.
  • AuthLite version 2.3.14 or later must be installed on your DCs and all ADFS server instances

AuthLite Configuration

  • There must be a setting on each ADFS server that forwards the 2-factor authentication from the Network layer to the S4U layer.  As of this writing, there's no user interface to do it.  So please create a registry group policy or directly edit the registry as follows:
    • Create a Computer setting (hive = HKEY_LOCAL_MACHINE)
    • the Key Path should be:
      Software\Policies\Collective Software\AuthLite
    • The Value name should be:
      TwoFactorProcessesS4UTransfer
    • The value data should be:
      IdentityServer
  • Ensure you link the group policy in a manner to affect the ADFS servers.
  • Use the Deny Access to this computer from the Network group policy  to block AuthLite users from connecting with 1-factor logon.
  • Please download API.ps1, and run the following command to turn on UPN Support (as of this time there is no user interface to do it)

    .\API.ps1 SetPartitionSetting -name UPNSupport -value true -reload $true

    Note the "$" difference between the value and the reload arguments!


    Note: This setting will take up to 20 minutes plus replication delay to be seen by all ADFS servers.

     

Testing

  • After a "gpupdate" on the ADFS servers, your AuthLite users should be unable to log in with UPN and password any more.
  • They *should* be able to log in by entering their normal password followed by a dash (minus) and their OTP, all together in the password field.  (For YubiKey, the dash character is optional)

Note that all primary Office 365 authentications for AuthLite users will now require 2-factor, including the login that happens when registering a new device for email access.  (Once registered, the device will no longer require user authentication each  time).