Last Updated: November 19, 2025
The LoginTC RADIUS Connector is a complete two-factor authentication virtual machine appliance packaged to run within your corporate network.
This documentation guide shows administrators an overview of how LoginTC MFA works with Dell iDRAC, including installation guidelines, requirements, architecture, policies and settings.
Subscription Requirement
Your organization requires the Starter or Professional plan to use the LoginTC RADIUS Connector. Explore Pricing Plans
There are a wide variety of authentication mechanism users can use to perform MFA with Dell iDRAC.
Supported devices include :
Appliance not listed?
We probably support it. Contact us if you have any questions.
Compatibility Guide
Any other Dell iDRAC appliance which have configurable LDAP authentication are supported.

Prefer Reading a PDF?
Download a PDF file with configuration instructions:
The Appliance is very easy to configure with a rich web-based interface much like LoginTC Admin Panel.
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.
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.
Installation






https://172.20.221.105:8443):



NOTE
These instructions assume a new environment. For a complete 2.X / 3.X to 4.X upgrade guide: LoginTC RADIUS Connector Upgrade Guide
| Port | Protocol | Purpose |
|---|---|---|
| 1812 | UDP | RADIUS authentication |
| 443 | TCP | API traffic |
| 8443 | TCP | Web interface |
logintc-user is 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 https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol>LDAP-speaking device with an optional first factor and LoginTC as a second factor. Each endpoint has 4 Sections:
1. LoginTC SettingsThis 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 DirectoryThis 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 / PassthroughThis 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 SettingsThis section describes which LDAP-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:
Configuration values:
| Property | Explanation |
|---|---|
Application ID |
The 40-character Application ID, retrieve Application ID |
Application API Key |
The 64-character Application API Key, retrieve Application API Key |
Request Timeout |
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 LDAP client. We recommend setting the Request Timeout value to 60 seconds in the LoginTC RADIUS Connector and setting the LDAP authentication server timeout to 70 seconds in LDAP Client. Not all LDAP clients support a timeout setting.
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:
Configuration values:
| Property | Explanation | Examples |
|---|---|---|
host |
Host or IP address of the LDAP server | ldap.example.com or 192.168.1.42 |
port (optional) |
Port if LDAP server uses non-standard (i.e., 389/636) |
4000 |
bind_dn |
DN of a user with read access to the directory | cn=admin,dc=example,dc=com |
bind_password |
The password for the above bind_dn account | password |
base_dn |
The top-level DN that you wish to query from | dc=example,dc=com |
attr_username |
The attribute containing the user’s username | sAMAccountName or uid |
attr_name |
The attribute containing the user’s real name | displayName or cn |
attr_email |
The attribute containing the user’s email address | mail or email |
LDAP Group (optional) |
The name of the LDAP group to be sent back to the authenticating server. | SSLVPN-Users |
encryption (optional) |
Encryption mechanism | ssl or startTLS |
cacert (optional) |
CA certificate file (PEM format) | /opt/logintc/cacert.pem |
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:
Configuration values:
| Property | Explanation | Examples |
|---|---|---|
IP Address or Host Name |
Host or IP address of the RADIUS server | radius.example.com or 192.168.1.43 |
Authentication Port (optional) |
Port if the RADIUS server uses non-standard (i.e., 1812) |
1812 |
Shared Secret |
The secret shared between the RADIUS server and the LoginTC RADIUS Connector | testing123 |
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.
Configuration values:
| Property | Explanation | Examples |
|---|---|---|
Challenge Groups (Optional) |
Comma separated list of groups for which users will be challenged with LoginTC | SSLVPN-Users or two-factor-users |
Challenge Groups (Optional) |
Comma separated list of groups for which users will always bypass LoginTC | NOMFA-Users |
Click Test to validate the values and then click Next.
Configure LDAP client (e.g. your LDAP-speaking endpoint:
Client configuration values:
| Property | Explanation | Examples |
|---|---|---|
name |
A unique identifier of your RADIUS client | CorporateVPN |
IP Addresss |
The IP address of your LDAP client (e.g. your LDAP-speaking endpoint). Add additional IP Addresses by clicking plus. | 192.168.1.44 |
Under Authentication Mode select Direct
| Property | Explanation | Examples |
|---|---|---|
Excempt Primary Bind |
When enabled, multi-factor authentication is skipped for the first successful LDAP authentication in each connection. This is useful when the device initially binds with a service account before authenticating the actual user. | No |
Excempt Users |
Users matching specified usernames or distinguished names will be exempt from multi-factor authentication. Use this option when the device first connects with a service account, disconnects, and then re-establishes a new LDAP connection to authenticate the actual user. | None |
Normalize Usernames |
Specify whether usernames like “DOMAIN\john.doe” and “john.doe@example.com” are treated as-is or as simply “john.doe”. This should be set to yes. | Yes, normalize usernames |
Enable Monitor User |
Specify a username that will not require LoginTC authentication. Use this setting if the device connecting performs monitoring of LDAP connections and always expects a successful bind. | No |
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):

Once you are satisfied with your setup, configure your RADIUS device to use the LoginTC RADIUS Connector as its RADIUS authentication source. Set the RADIUS timeout to 90 seconds to allow enough time for LoginTC authentication responses.
For your reference, the appliance web interface Settings page displays the appliance IP address and LDAP ports:

The following are quick steps to protect your Dell iDRAC logins with LoginTC. The instructions can be used for all LDAP supported iDRAC versions.






| Property | Explanation | Example |
|---|---|---|
Enable Certificate Validation |
Indicated whether to check the LDAP certificate being served by the LoginTC RADIUS Connector. We recommend turning this on, these instructions have it turned off. | checked |
Upload Directory Service CA Certificate |
Specify the CA certificate served by the LoginTC RADIUS Connector. This can be found under SETUP > Settings > RADIUS/TLS (RadSec) Server Certificate . |
certificate file |

| Property | Explanation | Example |
|---|---|---|
Enabled Active Directory |
Whether Active Directory is enabled as a user authentication method. Should be checked. | checked |
User Domain Name |
The active directory domain that will be searched by LDAP. Can use existing AD domain name | ubiquitous.cyphercor-labs.com |
Timeout |
Timeout in seconds to wait for the LoginTC RADIUS Connector to process the request. Recommended 50-70 seconds. | 50 |
Specify Domain Controller Addresses |
IP Address of the LoginTC RADIUS Connector, which is acting as an LDAP proxy. | 10.0.10.163 |

| Property | Explanation | Example |
|---|---|---|
Specify Global Catalog Server Addresses |
IP Address of the LoginTC RADIUS Connector, which is acting as an LDAP proxy. | 10.0.10.163 |
Standard Schema Role Groups |
Specify active directory group the user must be a member of and corresponding role. | idrac-super-users |
To test, navigate to your Dell iDRAC portal, select the correct Domain and attempt access.
Login Domain
Enabling Microsoft Active Directory will not disabled root access to iDRAC in case of misconfiguration. Simply select This iDRAC to login using root credentials, if present.
Since the Authentication Mode is set to Direct the authentication options are:
password,OTPpassword,OTPpassword,OTPpassword,bypasscodeCreate users in LoginTC corresponding to your AD/LDAP users and provision them tokens. There are several options for managing your users within LoginTC:
For more details about user management and provisioning, visit the User Management guide.
LoggingLogs can be found on the Logs tab:

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:

Email Support
For any additional help please email support@cyphercor.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. 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