5.2. RADIUS with Token Scenario Setup

This section describes how a typical multi-factor authentication scenario is configured. In this case, the scenario of RADIUS with username/password and token will be configured where a generated one time password (OTP) will be used as the additional authentication factor.

The first step is to go to Scenarios > RADIUS and then press the plus button on the scenario called Username, password and token.

Add RADIUS with Token Scenario

Figure 5.6. Add RADIUS with Token Scenario

A guide will now open to gather the required data for this scenario. In the first guide step, specify a suitable name for this scenario along with an optional description.

RADIUS with Token Scenario - Name and Description

Figure 5.7. RADIUS with Token Scenario - Name and Description

In the next guide step, select a user store. In this example, the LDAP store created in Chapter 4, LDAP Server Setup will be selected. It is also possible to select the Create new option to create a user store connection on the fly.

RADIUS with Token Scenario - User Store Selection

Figure 5.8. RADIUS with Token Scenario - User Store Selection

Now, specify a filter to find the user. In this case, it is enough to use the username. The Search base defines the root on the LDAP server where the users are found.

RADIUS with Token Scenario - LDAP User Filter

Figure 5.9. RADIUS with Token Scenario - LDAP User Filter

The RADIUS connection to use is now specified next. This determines the RADIUS requests that EasyAccess will listen for. In this example, the connection specified in Section 5.1, Basic RADIUS Scenario Setup is selected. Alternatively, a new RADIUS connection could be specified on the fly by selecting Create new.

RADIUS with Token Scenario - RADIUS Selection

Figure 5.10. RADIUS with Token Scenario - RADIUS Selection

The next guide step allows the acceptable IP addresses of connecting RADIUS clients to be specified. In addition the shared secret password that the client needs can be specified along with an optional Attribute Selector. The attribute selector is used if different authentication methods can be chosen. For example, a valid value might be 44=SMS.

RADIUS with Token Scenario - RADIUS Client Filter

Figure 5.11. RADIUS with Token Scenario - RADIUS Client Filter

Optionally specify that a PIN must appear either before or after the OTP, along with the user store attribute that will contain the code.

RADIUS with Token Scenario - PIN Code

Figure 5.12. RADIUS with Token Scenario - PIN Code

In the final guide step, select Create to save the scenario.

Create RADIUS Token Scenario

Figure 5.13. Create RADIUS Token Scenario

The EasyAccess server is now ready to accept authenticating RADIUS connections.