Azure Multi-Factor Authentication. KEMP LoadMaster and Azure Multi- Factor Authentication. Technical Note

(1)

KEMP LoadMaster

and Azure

Multi-Factor

(2)

Copyright Notices

KEMP Technologies, Inc. reserves all ownership rights for the LoadMaster product line including software and documentation. The use of the LoadMaster Exchange appliance is subject to the license agreement. Information in this guide may be modified at any time without prior notice.

Microsoft Windows is a registered trademarks of Microsoft Corporation in the United States and other countries. All other trademarks and service marks are the property of their respective owners.

Limitations: This document and all of its contents are provided as-is. KEMP Technologies has made efforts

to ensure that the information presented herein are correct, but makes no warranty, express or implied, about the accuracy of this information. If any material errors or inaccuracies should occur in this document, KEMP Technologies will, if feasible, furnish appropriate correctional notices which Users will accept as the sole and exclusive remedy at law or in equity. Users of the information in this document acknowledge that KEMP Technologies cannot be held liable for any loss, injury or damage of any kind, present or prospective, including without limitation any direct, special, incidental or consequential damages (including without limitation lost profits and loss of damage to goodwill) whether suffered by recipient or third party or from any action or inaction whether or not negligent, in the compiling or in delivering or communicating or publishing this document.

Any Internet Protocol (IP) addresses, phone numbers or other data that may resemble actual contact information used in this document are not intended to be actual addresses, phone numbers or contact information. Any examples, command display output, network topology diagrams, and other figures included in this document are shown for illustrative purposes only. Any use of actual addressing or contact information in illustrative content is unintentional and coincidental.

Portions of this software are; copyright (c) 2004-2006 Frank Denis. All rights reserved; copyright (c) 2002 Michael Shalayeff. All rights reserved; copyright (c) 2003 Ryan McBride. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE ABOVE COPYRIGHT HOLDERS ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or implied, of the above copyright holders..

(3)

Portions of this software are Copyright (C) 1988, Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.

Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.

2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.

(4)

1 Introduction

Multi-Factor Authentication (MFA) is a method of authentication that requires the use of more than one verification method and adds a critical second layer of security to user sign-ins and transactions. It works by requiring any two or more of the following verification methods:

 Something you know (typically a password)

 Something you have (a trusted device that is not easily duplicated, like a phone)  Something you are (biometrics)

Azure MFA is a method of verifying who you are that requires the use of more than just a username and password. It provides a second layer of security to user sign-ins and transactions. Azure MFA helps safeguard access to data and applications while meeting user demand for a simple sign-in process. It delivers strong authentication with a range of easy verification options – phone call, text message or mobile app notification – allowing users to choose the method they prefer.

Azure MFA is an easy to use, scalable and reliable solution that provides a second method of authentication so your users are always protected.

The security of multi-factor authentication lies in its layered approach. Comprising multiple authentication factors presents a significant challenge for attackers. Even if an attacker manages to learn the user’s password, it is useless without also having possession of the trusted device. Should the user lose the device, the person who finds it will not be able to use it unless they also know the user’s password.

1.1 Document Purpose

This document provides step-by-step instructions on how to configure Azure, the MFA server and the KEMP LoadMaster in order to provide multi-factor authentication.

This document uses an Exchange environment as an example scenario.

1.2 Intended Audience

(6)

Configure Azure Multi-Factor Authentication

2 Configure Azure Multi-Factor Authentication

Follow the steps in the sections below to configure Azure multi-factor authentication and the KEMP LoadMaster.

2.1 Create a Multi-Factor Authentication Provider in Azure

Follow the steps below to create a new multi-factor authentication provider in Azure: Log in to the Azure portal (classic).

Go to ACTIVE DIRECTORY.

Figure 2-1: QUICK CREATE

Select NEW.

(7)

Figure 2-2: CREATE

Enter a NAME for the authentication provider. Select the USAGE MODEL.

Select SUBSCRIPTION.

(8)

Figure 2-3: ACTIVE DIRECTORY

(9)

Figure 2-4: Configure Settings

(10)

Figure 2-5: Server

Click Server underneath the DOWNLOADS section on the left.

Download the Multi-Factor Authentication Server which will be run in your on-premises data center.

Do not click Generate Activation Credentials until you have installed the server on premises and are ready to activate the install. The Activation

Credentials are only valid for 10 minutes, at which time you would be required to obtain new credentials.

2.2 Install the Multi-Factor Authentication Server on Premises

The MFA server must be a member of the on-premises Active Directory domain. After

downloading the MFA server, install it on premises. When prompted, generate the Activation Credentials and enter them in the provided field.

Follow the steps below:

Launch the Multi-Factor Authentication Server console. Select Users.

(11)

Figure 2-6: Import

(12)

Figure 2-7: Edit User

(13)

2.3 Add the LoadMaster as a RADIUS Client

Follow the steps below to add the LoadMaster as a RADIUS client:

Select RADIUS Authentication within the Azure Multi-Factor Server.

Figure 2-8: RADIUS Authentication

(14)

2.4 Configure the LoadMaster

Follow the steps in the sub-sections below to configure the LoadMaster.

2.4.1 Increase the L7 Authentication Timeout

The L7 Authentication Timeout should be increased in order to provide enough time for the following actions to occur:

 The user enters their credentials

 Azure MFA communicates with the service in the cloud

 The service in the cloud sends the authentication to the user’s phone (via app or phone call)

To increase the L7 Authentication Timeout, follow the steps below:

In the main menu of the LoadMaster WUI, go to System Configuration > Miscellaneous Options > L7 Configuration.

Figure 2-10: L7 Authentication Timeout

Enter the L7 Authentication Timeout and click Set Timeout.

KEMP recommends 300 seconds but this can be adjusted as needed to meet requirements.

2.4.2 Create a New SSO Domain

Follow the steps below to create a new SSO domain:

(15)

Figure 2-11: Add new Client Side Configuration

Enter a name in the Add new Client Side Configuration text box and click Add.

Figure 2-12: Configure the domain

Select RADIUS as the Authentication Protocol.

Enter the IP address of the MFA Server in the RADIUS server(s) text box and click Set RADIUS Server(s). Multiple addresses can be entered in this text box, if required. Enter the RADIUS Shared Secret, which was created in the MFA configuration earlier, and click Set Shared Secret.

Enter the Domain/Realm and click Set Domain/Realm Name.

2.4.3 Configure the ESP Options in the SubVSs

Our example is based on using an Exchange environment. For this example scenario, the Edge Security Pack (ESP) Options for the OWA and Authentication Proxy SubVSs need to be

configured. To do this, follow the steps below:

(16)

Figure 2-13: ESP Options

Select Form Based as the Client Authentication Mode.

Select the SSO Domain that was created in the previous section. Configure any of the other settings as needed.

You may want to configure a custom SSO Image Set to inform users that MFA will be required. For further information on doing this, please refer to the Custom

Authentication Form, Technical Note.

Repeat the steps above to configure the other SubVS.

(17)

References

References

Unless otherwise specified, the following documents can be found at

http://kemptechnologies.com/documentation. ESP, Feature Description

(18)

Document History

Document History

Date Change Reason for Change Version Resp.

Azure Multi-Factor Authentication. KEMP LoadMaster and Azure Multi- Factor Authentication. Technical Note

KEMP LoadMaster

and Azure

Multi-Factor

Copyright Notices

Table of Contents

1 Introduction

1.1

Document Purpose

1.2

Intended Audience

2 Configure Azure Multi-Factor Authentication

2.1

Create a Multi-Factor Authentication Provider in Azure

2.2

Install the Multi-Factor Authentication Server on Premises

2.3

Add the LoadMaster as a RADIUS Client

2.4

Configure the LoadMaster

2.4.1

Increase the L7 Authentication Timeout

2.4.2

Create a New SSO Domain

2.4.3

Configure the ESP Options in the SubVSs

References

Document History