Two factor authentication for Microsoft Outlook Web App (OWA)

Overview

The LoginTC OWA Connector protects access to your Microsoft Outlook Web App by adding a second factor LoginTC challenge to existing username and password authentication.

User Experience

After entering the username and password into the Outlook Web App login, the user is shown a selection of second factor options. The user clicks a button to receive a LoginTC push notification, authenticates and is logged in.

Prefer Reading a PDF?

Download a PDF file with configuration instructions:

Subscription Requirement

Your organization requires the Business or Enterprise plan to use the LoginTC OWA Connector. See the Pricing page for more information about subscription options.

Prerequisites

Before proceeding, please ensure you have the following:

  • LoginTC Admin Panel account
  • Microsoft Windows Server 2012 R2 or Windows Server 2016
  • Exchange 2013 or Exchange 2016
  • .NET Framework 4.5.1 or higher

Working OWA Deployment

It is strongly recommended that you have a working and tested Outlook Web App deployment prior to adding LoginTC authentication.

Create Application

Start by creating a LoginTC Application for your deployment. An Application represents a service (e.g. An application is a service (e.g., VPN or web application) that you want to protect. e) that you want to protect with LoginTC.

Create a LoginTC Application in LoginTC Admin Panel, follow Create Application Steps.

If you have already created a LoginTC Application for your deployment, then you may skip this section and proceed to Installation.

Normalize Usernames

Usernames in RD Gateway are typically in the form “CORP.doe”, while in the LoginTC Admin Panel it is generally more convenient to simply use “john.doe”.

Configure Normalize Usernames from the Domain settings by navigating to Domains > Your Domain > Settings.

Select Yes, Normalize Usernames scroll down and click Update.

Installation

Follow the instructions to install the LoginTC OWA Connector:

  1. Download the latest version of the LoginTC OWA Connector
  2. Run the installer file as a privileged administrator user. The user must have permission to configure and restart IIS.
  3. Press Next.
  4. Read the License Agreement and press Next if you accept the terms.
  5. Change the LoginTC API Host only if you have a private enterprise LoginTC deployment. Press Next:
  6. Enter your LoginTC Application ID and Application API Key. These values are found on your LoginTC Admin Panel. Press Next.
  7. Choose a secret to use for encrypting and signing OWA sessions. If you already have a OWA secret key, then enter it. Press Next.
  8. Press Next.
  9. Press Finish

The LoginTC OWA Connector is now installed and protecting your Outlook Web App.

Usage

This chapter demonstrates the possibilities of the LoginTC OWA Connector from both an administrator’s and end user’s point of view.

The OWA initial login page where the user enters their username and password is unmodified.

After successfully authenticating with their username and password, the user is presented with options to log in with LoginTC. The user may select to authenticate using LoginTC push, bypass codes, or OTPs.

If the user selects LoginTC push, they are informed to approve the LoginTC requst on their device. The user is also presented with an option to remeber their LoginTC login choice. The next time the user logs in they will automatically receive a LoginTC push notification. The user may also cancel the login attempt and return to the login page.

The user is brought to their OWA homepage after successfully authenticating with LoginTC.

Logging

The LoginTC OWA Connector logs events to the Microsoft Event Viewer under Applications and Service Logs → LoginTC. LoginTC OWA Connector event logs are helpful in debugging issues.

Passthrough

Passthrough allows you to specify which set of users should be challenged with LoginTC second-factor authentication, and which ones will not. This is often useful when testing and when rollying out a deployment to minimize the impact on others.

Static User List

Setting a static user list tells the LoginTC OWA Connector which users must be challenged for LoginTC second-factor authentication. All other users will be passed through without requiring a second-factor authentication.

Instructions to set a static list of users to be challenged:

  1. Navigate to C:\Program Files\Cyphercor\LoginTC OWA Connector.
  2. Create a new file users.txt in Notepad.
  3. Populate the file with a list of users, one line at a time, in the following format: DOMAIN\username
  4. Save the file.
  5. Your change will be picked up by the connector within 60 seconds.

If the users.txt file does not exist then all users will be challenged with LoginTC second-factor authentication.

Group List

Setting a group list tells the LoginTC OWA Connector which AD security group members must be challenged for LoginTC second-factor authentication. All other users not belonging to any of the listed AD security groups will be passed through without requiring a second-factor authentication.

Instructions to set a list of AD security groups to be challenged:

  1. Navigate to C:\Program Files\Cyphercor\LoginTC OWA Connector.
  2. Create a new file groups.txt in Notepad.
  3. Populate the file with a list of AD security groups, one line at a time.
  4. Save the file.
  5. Your change will be picked up by the connector within 60 seconds.

If the groups.txt file does not exist then all users will be challenged with LoginTC second-factor authentication (unless a static user list file exists).

Architecture

Architecture and Authentication Flow

Architecture and Authentication Flow

Troubleshooting

Email Support

For any additional help please email support@cyphercor.com. Expect a speedy reply.