The LoginTC RADIUS Connector is a complete two-factor authentication virtual machine packaged to run within your corporate network. The LoginTC RADIUS Connector enables Apache to use LoginTC for the most secure two-factor authentication.Introduction
LoginTC makes it easy for administrators to add multi-factor to Apache. This document shows how to configure Apache to require two factor authentication for local and / or remote access via
mod_auth_radius Apache RADIUS authentication module. This guide was tested for Apache 2.2. For an alternate method using
mod_auth_xradius then you may be interested in: Two factor authentication for Apache using mod_auth_xradius.
Prefer Reading a PDF?
Download a PDF file with configuration instructions:
Before proceeding, please ensure you have the following:
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.
If you have already created a LoginTC Application for your deployment, then you may skip this section and proceed to Installation.Installation
These instructions assume a new environment. For a complete 2.X / 3.X to 4.X upgrade guide: LoginTC RADIUS Connector Upgrade Guide
|123||UDP||NTP, Clock synchronization (outgoing)|
logintc-useris used for SSH and web access. The default password is
logintcradius. You will be asked to change the default password on first boot of the appliance.
Endpoints describe how the appliance will authenticate your RADIUS-speaking device with an optional first factor and LoginTC as a second factor. Each endpoint has 4 Sections:1. LoginTC Settings
This section describes how the appliance itself authenticates against LoginTC Admin Panel with your LoginTC Application. Only users that are part of your organization and added to the domain configured will be able to authenticate.2. User Directory
This section describes how the appliance will conduct an optional first factor. Either against an existing LDAP, Active Directory or RADIUS server. If no first factor is selected, then only LoginTC will be used for authentication.3. Challenge Strategy / Passthrough
This section describes whether the appliance will perform a LoginTC challenge for an authenticating user. The default is to challenge all users. However with either a static list or Active Directory / LDAP Group you can control whom gets challenged to facilitate seamless testing and rollout.4. Client Settings
This section describes which RADIUS-speaking device will be connecting to the appliance and whether to encrypt API Key, password and secret parameters.
The web interface makes setting up an endpoint simple and straightforward. Each section has a Test feature, which validates each input value and reports all potential errors. Section specific validation simplifies troubleshooting and gets your infrastructure protected correctly faster.
Close the console and navigate to your appliance web interface URL. Use username
logintc-user and the password you set upon initial launch of the appliance. You will now configure the LoginTC RADIUS Connector.
Create a new endpoint file by clicking + Create your first endpoint:
A list of available Applications will be displayed from your LoginTC organization. Select which LoginTC Application to use:
Configure the application:
||The 40-character Application ID, retrieve Application ID|
||The 64-character Application API Key, retrieve Application API Key|
||Number of seconds that the RADIUS connector will wait for|
The Application ID and Application API Key are found on the LoginTC Admin Panel.
Make a note of what you set the Request Timeout to as you will need to use a larger timeout value in your RADIUS client. We recommend setting the Request Timeout value to 60 seconds in the LoginTC RADIUS Connector and setting the RADIUS authentication server timeout to 70 seconds in RADIUS Client. For more information see: Recommended settings for an optimal user experience for VPN access
Click Test to validate the values and then click Next:
Configure the user directory to be used for first authentication factor in conjunction with LoginTC. You may use Active Directory / LDAP or an existing RADIUS server. You may also opt not to use a first factor, in which case LoginTC will be the only authentication factor.
Active Directory / Generic LDAP Option
Select Active Directory if you have an AD Server. For all other LDAP-speaking directory services, such as OpenDJ or OpenLDAP, select Generic LDAP:
||Host or IP address of the LDAP server||
||Port if LDAP server uses non-standard (i.e.,
||DN of a user with read access to the directory||
||The password for the above bind_dn account||
||The top-level DN that you wish to query from||
||The attribute containing the user’s username||
||The attribute containing the user’s real name||
||The attribute containing the user’s email address|
||The name of the LDAP group to be sent back to the authenticating server.||
||CA certificate file (PEM format)||
Click Test to validate the values and then click Next.
Existing RADIUS Server Option
If you want to use your existing RADIUS server, select RADIUS:
||Host or IP address of the RADIUS server||
||Port if the RADIUS server uses non-standard (i.e.,
||The secret shared between the RADIUS server and the LoginTC RADIUS Connector||
Click Test to validate the values and then click Next.
Configure which users will be challenged with LoginTC. This allows you to control how LoginTC will be phased in for your users. This flexibility allows for seamless testing and roll out.
For example, with smaller or proof of concept deployments select the Static List option. Users on the static list will be challenged with LoginTC, while those not on the list will only be challenged with the configured First Authentication Factor. That means you will be able to test LoginTC without affecting existing users accessing your VPN.
For larger deployments you can elect to use the Active Directory or LDAP Group option. Only users part of a particular LDAP or Active Directory Group will be challenged with LoginTC. As your users are migrating to LoginTC your LDAP and Active Directory group policy will ensure that they will be challenged with LoginTC. Users not part of the group will only be challenged with the configured First Authentication Factor.
Challenge All Users
Select this option if you wish every user to be challenged with LoginTC.
Challenge Users Based on Static Username List
Select this option if you wish to have a static list of users that will be challenged with LoginTC. Good for small number of users.
LoginTC challenge users: a new line separated list of usernames. For example:
jane.doe jane.smith john.doe john.smith
Challenge Users Based on Group Membership
Select this option if you wish to have only users part of a particular Active Directory or LDAP group to be challenged with LoginTC. Good for medium and large number of users.
||Comma separated list of groups for which users will be challenged with LoginTC||
||Comma separated list of groups for which users will always bypass LoginTC||
Click Test to validate the values and then click Next.
Configure RADIUS client (e.g. your RADIUS-speaking VPN):
Client configuration values:
||A unique identifier of your RADIUS client||
||The IP address of your RADIUS client (e.g. your RADIUS-speaking VPN). Add additional IP Addresses by clicking plus.||
||The secret shared between the LoginTC RADIUS Connector and its client||
Under Authentication Mode select Direct
The LoginTC RADIUS Connector will directly and automatically perform the LoginTC second factor. See User Experience for more information.
Click Test to validate the values and then click Save.Testing
When you are ready to test your configuration, create a LoginTC user (if you haven’t already done so). The username should match your existing user. Provision a token by following the steps:
When you have loaded a token for your new user and domain, navigate to your appliance web interface URL:
Click Test Configuration:
Enter a valid username and password; if there is no password leave it blank. A simulated authentication request will be sent to the mobile or desktop device with the user token loaded. Approve the request to continue:
Congratulations! Your appliance can successfully broker first and second factor authentication. The only remaining step is to configure your RADIUS device!
If there was an error during testing, the following will appear:
In this case, click See logs (or click the Logs section):
mod_auth_radius module from FreeRADIUS is an Apache RADIUS authentication module. If your system does not have
mod_auth_radius installed you will need to do so. Below are instructions for RedHat. For more information on
mod_auth_radius and installing it on your system please see: FreeRADIUS mod_auth_radius Apache RADIUS authentication module.
mod_auth_radius on RedHat
Step 1: Developer tools:
$ sudo yum install httpd-devel gcc wget openssl openssl-devel -y
Step 2: Build
$ cd /tmp $ sudo wget ftp://ftp.freeradius.org/pub/radius/mod_auth_radius-1.5.8.tar $ sudo tar xvf mod_auth_radius-1.5.8.tar $ cd mod_auth_radius-1.5.8 $ sudo apxs -i -a -c mod_auth_radius-2.0.c
mod_auth_radius Apache RADIUS authentication module version 1.5.8
At the time of this document being written 1.5.8 was the latest version of the Apache RADIUS authentication module. For updates please see: FreeRADIUS mod_auth_radius Apache RADIUS authentication module.
/etc/httpd/modules/mod_auth_radius-2.0.sois installed and ready to configure Apache RADIUS Authentication Configuration
Step 1: Edit
/etc/httpd/conf/httpd.conf (or equivalent path):
$ sudo vi /etc/httpd/conf/httpd.conf
Ensure LoadModule is present:
LoadModule radius_auth_module /usr/lib64/httpd/modules/mod_auth_radius-2.0.so
Inside VirtualHost add:
This example exposes a
public URL protected by LoginTC and in turn reverse proxies to a
private URL. The
private URL can reverse proxy an application manager (i.e. Tomcat) or simply serve the HTML pages directly. Direct access to the
private is forbidden since it must come from 127.0.0.1 / localhost.
# AddRadiusAuth server:port shared_secret timeout[:retries] # Example server (change to fit your needs): AddRadiusAuth 192.168.1.40:1812 bigsecret 60:0 # AddRadiusCookieValid time_in_minutes AddRadiusCookieValid 60 <Location "/public"> AuthType Basic AuthName "Radius Authentication" AuthBasicProvider "radius" AuthRadiusAuthoritative on AuthRadiusCookieValid 1 AuthRadiusActive On require valid-user ProxyPass http://localhost/private ProxyPassReverse http://localhost/private </Location> <Location "/private"> Order deny,allow Deny from all ProxyPass http://localhost:8080/mytomcatapp ProxyPassReverse http://localhost:8080/mytomcatapp Allow from 127.0.0.1 Allow from localhost </Location>
Step 4: Restart
$ sudo service httpd restart
You are now ready to test two-factor authentication to Apache.Testing Apache
Test by accessing the protected URL in your browser. The username of the Apache user must match the username of the user created in your LoginTC organization and added to the domain you have configured to authenticate against.
You will be prompted for basic authentication and then challenged with LoginTC.User Management
There are several options for managing your users within LoginTC:
Logs can be found on the Logs tab:
For troubleshooting related to the
mod_auth_radius Apache RADIUS authentication module please refer to: FreeRADIUS mod_auth_radius Apache RADIUS authentication module.
If you are unable to authenticate, navigate to your appliance web interface URL and click Status:
Ensure that all the status checks pass. For additional troubleshooting, click Logs:
Also make sure to check the Apache logs and secure logs on the Linux machine hosting Apache (
For any additional help please email email@example.com. Expect a speedy reply.
NOTE: Upgrade time
Upgrade can take 10-15 minutes, please be patient.
Important: LoginTC RADIUS Connector 3.X End-of-life
The LoginTC RADIUS Connector 3.X virtual appliance is built with CentOS 7.9. CentOS 7.X is End of Lifetime (EOL) June 30th, 2024. See CentOS Product Specifications. Although the appliance will still function it will no longer receive updates and nor will it be officially supported.
New LoginTC RADIUS Connector 4.X
A new LoginTC RADIUS Connector 4.X virtual appliance has been created. The Operating System will be supported for many years. Inline upgrade is not supported. As a result upgrade is deploying a new appliance. The appliance has been significantly revamped and although the underlying functionality is identical, it has many new features to take advantage of.
Complete 3.X to 4.X upgrade guide: LoginTC RADIUS Connector Upgrade Guide