Documentation

 

 

Introduction

Security Notice

A critical security vulnerability affects SecureAuth Login for Windows version 1.0. SecureAuth recommends all users upgrade to version 1.0.1 (or later) immediately.

SecureAuth Support representative, refer to SecureAuth Security Bulletin SA-2018-01 (SecureAuth Login for Windows) for details.

Login for Windows (available in SecureAuth IdP version 9.2+ only) adds SecureAuth’s Multi-Factor Authentication to the Windows desktop and remote server login experience. This product was introduced in SecureAuth IdP version 9.2 and supports these authentication methods:

  • Timed Passcode
  • Voice Call
  • Passcode sent via SMS / Text Message
  • Passcode sent via Email
  • One-time Passcode via Push Notification
  • Login Notification via Push Notification
  • YubiKey HOTP Device Passcode
  • Passcode from Help Desk

NOTE: Methods delivered via Push Notification require the use of the SecureAuth Authenticate App.

In addition to the supported Multi-Factor Authentication methods, Login for Windows supports these setups / features:

  • Offline mode login
  • Multi-Factor Authentication for desktops and / or remote servers
  • Multi-Factor Authentication for single users only and / or multi-users
  • Users in bypass group can skip Multi-Factor Authentication
  • Bypass group lookup on a domain other than user's domain
  • Password expiration notification
  • Password Reset link to SecureAuth IdP realm or 3rd party service
  • Multiple login capability
  • Endpoint identified during login Multi-Factor Authentication request
  • Use Third-party Credential Providers
  • YubiKey HOTP support for 2-Factor Authentication
  • TOTP 2-Factor Authentication
  • Cached user credentials let users sign in with fewer clicks
  • Installation API validation
  • Adaptive Authentication
  • Validated with FIPS 140-2 compliant cryptographic libraries

Refer to the Release notes for information about releases.

DISCLAIMERS:

  • Login for Windows does not support non-domain joined devices. Issues pertaining to account synchronization are the responsibility of the customer and not SecureAuth.
  • Login for Endpoints ONLY supports the samAccountName login name format; userPrincipalName (UPN) is not supported.
    Note that UPN is supported at login, but if using a non-AD profile store containing OATHSeed/OATHToken/PNToken but not samAccountName, then the Multi-Factor Authentication lookup will fail and the user will not be able to use other Multi-Factor Authentication methods.

 


Prerequisites

Administrator

Setup requirements

1. Ensure SecureAuth IdP v9.2 or later is running and is using a SHA2 (or later) certificate.

2. Create a new realm or access an existing realm on which more than one Multi-Factor Authentication is required.

NOTE: This realm should not be configured for Single Sign-on.

3. Configure these SecureAuth IdP Web Admin tabs: Overview, Data, Workflow, Multi-Factor Methods, Post Authentication, and Logs.

4. Ensure target end-user machines are running any of the following supported OS versions:

Supported OS Versions

Windows OS versions:

  • Windows 7 (32/64-bit)
  • Windows 8.1 (32/64-bit)
  • Windows 10 (64-bit)

Windows Server OS versions:

  • Windows Server 2008 R2 (64-bit)
  • Windows Server 2012 (64-bit)
  • Windows Server 2012 R2 (64-bit)
  • Windows Server 2016 (64-bit)

See SecureAuth Compatibility Guide for OS and SecureAuth IdP version support information.

NOTE: To use the proxy bypass feature with Windows, a proxy server and proxy bypass list must be configured. See Login for Windows Installer Configuration for information about configuring the proxy server and proxy bypass list.

Verify TLS 1.1 and TLS 1.2 enablement via GPO on Windows Server OS

Verify TLS 1.1 and TLS 1.2 are enabled via the Group Policy Object (GPO) to ensure a streamlined and secure login experience for users logging on a Remote Desktop.

The external article How to Enable TLS 1.1 and TLS 1.2 in Internet Explorer via Group Policy provides instructions on how to enable TLS 1.1 and TLS 1.2.

NOTE: TLS 1.1 and TLS 1.2 are not enabled by default on Windows Server 2008 R2.

End-user

First-time usage requirements

SecureAuth strongly recommends using a timed passcode the first time you use Login for Windows to access the network.

To meet this requirement, you must have an account provisioned with a SecureAuth IdP realm that enables your device to generate timed passcodes for Multi-Factor Authentication:

Thereafter, you can use Login for Windows in the offline mode.

NOTE: If you are currently using the SecureAuth Credential Provider, you do not need to uninstall it before installing Login for Windows.

 


SecureAuth IdP Web Admin configuration

Data tab

1. Create a new realm and configure a data store on the Data tab.

2. In the Membership Connections Settings section, under Group Permissions, select False from the Advanced AD User Check dropdown.

3. Select Bind from the Validate User Type dropdown.

4. In the Profile Fields section, enter adminDescription in an unused Aux ID field—Aux ID 3 in this example—and make the field Writable.

5. If using a single OATH seed for end-user Multi-Factor Authentication (see sample Post Authentication page image), then map Fields to OATH Seed and OATH Tokens Properties, as shown in the Profile Fields image below.

 Sample image from Post Authentication page showing Single OATH Seed setting...

 

 

6. Click Save.

Optional: Adaptive Authentication tab

NOTE: Adaptive Authentication can be used to control the user login experience and to mitigate security risks.

The order of priority to handle user authentication login requests using Adaptive Authentication is as follows:

A. Threat Service

B. IP whitelist / blacklist

C. Geo-location

D. Geo-velocity

E. User / Group

NOTE: See Group Bypass configuration notes in the Login for Windows Installer configuration section for information about using Adaptive Authentication with the group bypass feature.

Multi-Factor Methods tab

7. In the Multi-Factor Configuration section, configure the Multi-Factor Authentication methods you want enabled.

8. Click Save.

System Info tab

9. On the System Info tab, in the Links section, Click to edit Web Config file.

10. In the Web Config Editor section, under <appSettings>, add this line:

    <add key="OTPFieldMapping" value="AuxID#" />

NOTE: In this example, AuxID3 is used since this Property was selected and configured on the Data tab in step 4.

11. Click Save.

API tab

12. In the API Key section, click Generate Credentials.

The API ID and API Key are required and used in the config.json file for all scenarios of using this product.

13. In the API Permissions section, select Enable Authentication API.

NOTE: It is not recommended to enable Identity Management options since the password reset function uses an IdP realm or third party password reset URL—not the Identity Management API.

14. Click Save once the configuration is complete.

15. Select Enable Login for Endpoints API, and then click Configure Login for Endpoints Installer.

Login for Windows Installer Configuration 

16. On the Login for Endpoints Installer Configuration page, select Windows as the Endpoint Operating System.

17. Select the Endpoint Type to specify that either a single user or multiple users can log on the device.

NOTE: For the single user selection, once the user has successfully logged on the endpoint online, thereafter the user can log on the endpoint offline without an Internet connection.

18. Enter the IdP Hostname.

19. Under Multi-Factor Authentication Settings, specify whether the user must use Multi-Factor Authentication to access the device from a desktop and / or remote desktop session.

20. If any user group is allowed to bypass Multi-Factor Authentication, enable the bypass option and list the user group(s).

Group Bypass configuration notes:

  • If using Adaptive Authentication AND the group bypass feature, the group bypass feature takes precedence for handling the user's login request.
  • In a multi-forest AD environment, the user account must be included on each domain in order to bypass Multi-Factor Authentication on any domain.

Proxy Server and Proxy Server and Proxy Bypass List configuration notes:

If using a proxy bypass, you must configure the proxy server and proxy bypass list – i.e. a list of hosts to use to bypass the proxy.

The following order is used:

A. "proxy_server" and "proxy_bypass" configuration from config.json file – these settings are derived from entries made in the Web Admin Login for Endpoints Installer Configuration section.

B. Windows proxy configuration – see https://msdn.microsoft.com/en-us/library/windows/desktop/aa384069(v=vs.85).aspx

21. If enabling Password Reset, specify either the SecureAuth IdP realm or the web page URL the user can access for resetting a password.

22. If Alternate Credential Providers are permitted, specify if non-SecureAuth credential providers and other credential providers such as card scanners can be used.

Alternate Credential Provider notes: 

  • By enabling alternate credential providers, users will be able log in without using the Login for Windows credential provider, and potentially bypass Multi-Factor Authentication.
  • Enabling alternate credential providers is only recommended in test environments, to let testers bypass Login for Windows so they can readily access their machines.
  • If the default Windows Credential Provider is enabled, users will see their normal login prompt and will have to manually select a different login option in order to use Login for Windows.

23. Click Download Installer Config to download the JSON file (config.json) which must first be configured before it can be used with the MSI file, as described in the Installation section of this guide.

NOTE: Before installation, config.json must be edited if the end-user is not always required to use Multi-Factor Authentication for logging on a local console and / or remote console – see the Set end-user access level section for access level settings and configuration.

 


Pre-installation steps 

Optional: Set end-user access level 

Login for Windows requires the end-user to use Multi-Factor Authentication by default to access the local console or remote console in an RDP session.

Before installing Login for Windows on the end-user's (target) machine, the config.json file must be edited if you wish to change the end-user's login access level setting.

Change the user's access level

1. Find the config.json file you downloaded in step 23 of the Web Admin Configuration section of this document, and copy that file to the Temp folder on the target machine.

2. Start a text editor such as Notepad++ and edit the access_level in the file, changing the value to a pertinent value:

  • 0 = Multi-Factor Authentication always required
  • 1 = Multi-Factor Authentication required for local access only
  • 2 = Multi-Factor Authentication required for remote access only
  • 3 = Multi-Factor Authentication never required – this setting is used for Self-service Password Reset (SSPR) only

3. Save the configuration.

Verify "allow_self_signed" setting

Find the config.json file you downloaded in step 23 of the Web Admin Configuration section of this document, and verify the setting for "allow_self_signed". You may need to change this setting based on how users will log on your environment.

Setting "allow_self_signed" to True is commonly used in test or lab environments in which the server has a self-signed certificate. This setting is not supported in a production environment since it introduces critical security risks, namely the potential "Man in the middle" attack which grants users access to a system without validating their credentials, and lets unauthorized users steal OATH seeds.

Note that once installing an endpoint with "allow_self_signed" set to True, this setting remains effective until Login for Endpoints is uninstalled and then re-installed using a configuration file with "allow_self_signed" set to False

 


Installation steps

Download and run the Login for Windows MSI package

1. Download the Login for Windows .zip file to the target machine (laptop, desktop, server, etc.).

2. Unzip the file.

3. Within the Login for Windows folder, find the .msi file for your machine — SecureAuthLogin-1.x.x-x64.msi or SecureAuthLogin-1.x.x-x86.msi — and place that file in the Temp folder.

Install Login for Windows

IMPORTANT: On a Windows server, SecureAuth Login for Windows should only be installed / uninstalled from a console session and not an RDP session.

1. Find the config.json file which you downloaded in step 23 of the Web Admin Configuration section of this document, and copy that file to the Temp folder on the target machine.

NOTE: You may have already performed this step if you changed the user's access level in the Set End-user Access Level section above.

2. On the target machine, run the following command line with administrator permissions, using the file name of your .msi file and correct path of that file on your machine, as in this example:

    msiexec /i "C:\Temp\SecureAuthLogin-1.0.0-x64.msi" /L*V "C:\Temp\install.log" /qn CONFIG="C:\Temp\config.json"

3. Log off the target machine.

After this installation, SecureAuth Login for Windows appears on the next login session.

NOTES:

  • If using Login for Windows in a PCI environment, see Login for Windows SSL configuration requirements if Login for Windows is not installing on a machine.
  • If reinstalling Login for Windows immediately after unstalling the software, the "Failed to write configuration" message will appear if the installer is not finished performing cleanup tasks such as removing the C:\ProgramData\SecureAuth directory.

SecureAuth IdP transaction log information

The Login for Windows software issues a User-Agent HTTP Request Header when the Application Programming Interface interacts with SecureAuth IdP. The following items are included in the UserAgent string:

  • Login for Windows software version
  • OS version
  • Computer name (hostname)
  • Time Zone
  • IP address
  • MAC address

For example:

   SecureAuthLogin for Windows 10.5.2 (Windows 10 Pro x64 6.2.9200; LT-JSMITH; (UTC-05:00) Eastern Standard Time; 111.22.333.44; 0f:10;35:7a:81:4e)

Uninstallation

On the target machine, run the following command line with administrator permissions, using the file name of your .msi file and correct path of that file on your machine: 

   msiexec /x "<msi>" /L*V "uninstall.log" /qn

NOTE: Manual installation on Windows 10 using the "Programs and Features" menu will result in an error.

 


End-user login experience on Windows 10

Known Issues

  • On Windows 10 desktops, a Login Notification request cancelled on the desktop—but accepted on the SecureAuth Authenticate app on a mobile device—still gives the user login access on the machine. This issue has been raised with Microsoft, but at this time remains unaddressed by them.
  • On Windows Server versions 2008 R2 and 2012 R2, users may be unable to complete the self-service password reset process due to default Internet Explorer settings in the operating systems.
  • If using a proxy which becomes unavailable, Login for Windows behaves as if it is offline. This issue may impact laptop users who connect their laptops to networks in which the proxy is unavailable.
  • The Self-Service Password Reset feature – which opens a browser to a Self-Service Password Reset page – does not function in environments using a proxy to access SecureAuth IdP. In these scenarios, contact SecureAuth Support and inquire about workarounds. Note this feature differs from the inline password reset feature that is used when a user’s password expires – this feature functions properly in proxy environments.

  • The Self-service Password Reset may not function correctly for certain operating systems. On Windows Server versions 2008 R2 and 2012 R2, users are unable to complete the self-service password reset process due to default Internet Explorer settings in the operating systems.

First-time login experience

1. Enter your username on the Windows login screen.

2. The first time you use Login for Windows, SecureAuth recommends selecting a timed passcode authentication option from the list of Multi-Factor Authentication methods for which you have enrolled. This could be one that uses the SecureAuth Authenticate App on your mobile device or another device provisioned with the SecureAuth IdP realm to supply timed passcodes, such as a YubiKey

After selecting a timed authentication option and entering your password, the timed passcode option will be available for you to use when logging on this machine offline.

If you do not have an authentication method that provides a timed passcode, then select any other option available to you.

FieldsInstructions

Timed passcode from app

For this option:

1. If there is more than one provisioned OATH OTP app, select the device.

2. Enter your Windows Password.

3. Click the arrow to log on Windows.

Passcode from voice call

For this option:

1. Select the phone number if more than one mobile phone is included in your user profile.

2. Enter your Windows Password.

3. Click the arrow to log on Windows.

Passcode from SMS / text

For this option:

1. Select the phone number if more than one mobile phone is included in your user profile.

2. Enter your Windows Password.

3. Click the arrow to log on Windows.

Passcode from email

For this option:

1. Select the email address if more than one address is included in your user profile.

2. Enter your Windows Password.

3. Click the arrow to log on Windows.

Passcode from notification

For this option:

1. Select the mobile device on which the provisioned SecureAuth Authenticate app is installed.

2. Enter your Windows Password.

3. Click the arrow to log on Windows.

Approve login notification on mobile

For this option:

1. Select the mobile device on which the provisioned SecureAuth Authenticate app is installed.

2. Enter your Windows Password.

3. Click the arrow to log on Windows.

Contact help desk for passcode

For this option:

1. Select the phone number to use for contacting the help desk.

2. Enter your Windows Password.

3. Click the arrow to log on Windows.

Passcode from token

For this option:

1. If there is more than one provisioned token, select the device on which the provisioned SecureAuth passcode app is stored.

2. Enter your Windows Password.

3. Click the arrow to log on Windows.

Subsequent login experience

When logging on the same machine in subsequent sessions, the Login for Windows page includes a selection of all Multi-Factor Authentication methods for which you enrolled.

The login screen defaults to the authentication method used in the last login session.

Sign-in Option IconsFieldsInstructions

Timed passcode from app

1. In the Enter passcode field, enter the OATH OTP from your SecureAuth One-time Passcode app.

2. Click the arrow to log on Windows.

Contact help desk for passcode

1. Enter the passcode received by contacting the help desk.

2. Click the arrow to log on Windows.

Approve login notification on mobile

1. Accept the login notification sent to the SecureAuth Authenticate app on your mobile device.

2. Access Windows.

Passcode from notification

1. Enter the passcode sent to the SecureAuth Authenticate app on your mobile device.

2. Click the arrow to log on Windows.

Passcode from email

1. Enter the passcode sent to your email address.

2. Click the arrow to log on Windows.

Passcode from voice call

1. Enter the passcode received by a voice call to your mobile phone.

2. Click the arrow to log on Windows.

Passcode from SMS / text

1. Enter the passcode sent via SMS to your mobile phone.

2. Click the arrow to log on Windows.

Passcode from Token

1. Plug in the token to receive a passcode from the device.

2. Click the arrow to log on Windows.

 


Release notes 

 

Version 1.0.3 - Release Date: September 17, 2018

New features and enhancements

CP-459A warning message now appears to end-users if the 'allow_self_signed' flag is enabled in config.json.

Resolved issues

CP-447An empty screen without login functionality no longer appears after installation.

Known issues

CP-288Login for Window performance degradation when loading the login screen in the offline mode on Windows 10.
CP-386SMS / Voice telephone numbers are not completely masked for registered Multi-Factor Authentication methods.
CP-414User details are missing when choosing a registered user on the "Other user" login screen
CP-416Manual uninstallation from the "Programs and Features" menu on Windows 10 results in an error.
CP-443User is given a private IP address when Adaptive Authentication is used in an RDP session.
CP-447Non-local user whose account is not found in Active Directory receives an empty login screen.
CP-457User is blocked by Adaptive Authentication on Windows Server 2012 R2 and receives an error message if no alternate providers are configured.
CP-470The last user displays even with the multiple_user flag set.
CP-472Adaptive Authentication login error after Login for Windows installation on Windows 7.
Version 1.0.2 - Release Date: June 13, 2018

Resolved issues and enhancements

CP-187RDP users utilizing NLA (Network Level Authentication) no longer receive a second prompt after providing credentials to the RDP client.
CP-267The Multi-Factor Authentication device order now remains consistent on subsequent login attempts.
CP-320Login for Windows now remembers the most recently entered login username on a non-server.
CP-340An active hover link now appears when attempting to select another Multi-Factor Authentication method.
CP-339The correct HOTP icon now appears on passcode entry window.
CP-379Log details have been added to help troubleshoot common installation errors.
CP-388Users in offline mode now correctly receive Multi-Factor options that are usable offline.
CP-393Re-installing Login for Windows now applies configuration file updates.
CP-398The installer error message for a missing configuration file has been revised for clarification.
CP-400First-time users must now use an OATH-based method (if enrolled in one) to ensure at least one OATH seed is cached for offline use.
CP-403The most recently used Multi-Factor Authentication device now appears when logging on / off Windows 7 or Windows 10.
CP-408SADiag.exe no longer returns an error when 'set logging off' and 'test api' log level settings are used.
CP-410The installer now accepts a relative path to the configuration file during a silent installation.
CP-411The correct username now appears on the lock screen on Windows 7 / Windows Server 2008.

Known issues

CP-386SMS / Voice telephone numbers are not completely masked for registered Multi-Factor Authentication methods.
CP-414User details are missing when choosing a registered user on the "Other user" login screen
CP-416Manual uninstallation from the "Programs and Features" menu on Windows 10 results in an error.
Version 1.0.1 - Release Date: May 14, 2018

Resolved issues

  • Incorrect IP addess used for Adaptive Authentication

When logging on locally, SecureAuth IdP now correctly uses the endpoint's public-facing IP address instead of a local adaptor IP address.

In this issue, a private IP address was being used which prevented IP-related Adaptive Authentication features from functioning properly. Remote / RDP logins were not impacted by this issue.

  • AD bad password count incorrectly incremented 

When attempting to log on using a bad password, the bad password count now increments appropriately – i.e. one time for each login attempt.

In this issue, the Active Directory bad password count would increment multiple times for a single login attempt, causing the user to be locked out immediately or sooner than anticipated. In certain scenarios, the bad password count incremented once for each OATH seed-based Multi-Factor Authentication method – e.g. for each app-based OTP or hardware token.

  • Re-installation breaks login functionality

Login for Windows can now be re-installed on the same machine.

In this issue, the Login for Windows software could become corrupted if re-installed on a machine which already had the software installed. This issue prevented users from logging in and required the user to boot up the machine in safe mode to repair the software.

  • Non-proxy aware

Beta support is now available for proxies in Login for Windows – see Login for Windows Installer Configuration to configure Login for Windows 1.0.1 for use with a proxy. Note the known issues when using a proxy in the 1.0.1 release.

This issue affected environments in which direct access to the SecureAuth IdP appliance is blocked and users must use a proxy.

  • Login failure for users with a space in sAMAccountName 

The issue has been resolved for users who were unable to log in if a space exists in their sAMAccountName property. 

  • Users in a bypass group unable to use Self-Service Password Reset function

The Self-Service Password Reset link now appears for users who are in a bypass group. 

Known issues

  • Installation requires an absolute path to the configuration file

The installer does not accept a relative path to the configuration file, which prevents deploying the installer from a directory that cannot be defined in advance (such as when using a Group Policy).

  • Potential offline lockout for new users

To use the offline mode, a user must first use an OATH-based authentication method – such as a one-time code (OTP) generated by the SecureAuth Authenticate App – at least one time while online in order to cache the OATH seed used for authenticating the user. SecureAuth recommends instructing users how to enable the offline mode before they attempt to go online.

A future release of Login for Windows will address the potential new user lockout issue by providing guidance to users during the login process.

  • Double prompting for RDP logins

Users utilizing NLA (Network Level Authentication) when logging on a system with RDP enabled may still be prompted for a username and password once the session is established.

  • Self-service Password Reset function is non-proxy aware

The Self-service Password Reset feature – which opens a browser to a Self-Service Password Reset page – does not function in environments using a proxy to access SecureAuth IdP.

In these scenarios, contact SecureAuth Support and inquire about workarounds.

Note this feature differs from the inline password reset feature that is used when a user’s password expires – this feature functions properly in proxy environments. 

  • Self-service Password Reset may not function correctly for certain Operating Systems

On Windows Server versions 2008 R2 and 2012 R2, users are unable to complete the self-service password reset process due to default Internet Explorer settings in the operating systems.

  • Offline endpoint when proxy is unavailable

Use of any proxy configured for Login for Windows becomes mandatory. If the proxy is unavailable, Login for Windows behaves as if it is offline.

This issue may impact laptop users who connect their laptops to networks in which the proxy is unavailable.

  • Re-installing Login for Windows does not apply configuration file updates

Re-running the installer with a new or updated configuration file does not result in configuration changes made to the current installation. Administrators must uninstall and then re-install Login for Windows to apply the new settings.

  • SMS and Voice numbers are not correctly masked

Users prompted for Multi-Factor Authentication can view the full telephone number for a registered Multi-Factor Authentication method.

  • Incorrect username shown on lock screen

Users in a bypass group are shown the wrong username on a Windows 7 workstation lock screen.

 

Version 1.0 - Release Date: February 1, 2018

The new Login for Windows product gives end-users a secure login experience on a Windows workstation, or on a remote Windows server, using a SecureAuth Multi-Factor Authentication method. This product, with FIPS 140-2 compliant cryptographic libraries, is newly designed and engineered and replaces the Credential Provider application. After the initial setup and first-time usage, the end-user subsequently logs on without a password by just using a 2-Factor Authentication method. 

 


Related documentation

YubiKey HOTP Device Provisioning and Multi-Factor Authentication Guide

SecureAuth Credential Provider Configuration Guide

Login for Endpoints Configuration Guide v1.0.2

Login for Mac configuration guide v1.0.3

Login for Windows SSL configuration requirements

 

 

  • No labels