RADIUS Authentication Explained: A Technical Overview

Approximately 79% of Chief Information Security Officers (CISOs) cite “human risk” as their largest cybersecurity risk. Given that a network is only as strong as its weakest link, enterprises that conduct business online need to ensure robust network security.

WPA2- and WPA3-Enterprise with 802.1X represent the gold standard for wireless authentication, and Remote Authentication Dial-In User Service (RADIUS) servers play an integral part.

RADIUS is imperative for securely authenticating users on a network access server. It also allows organizations to use unique authentication keys for each user, rather than one single pre-shared key like we use with our home Wi-Fi. Read here about how a marketing firm successfully secured its offices globally with our Cloud RADIUS.

This article covers RADIUS authentication at a high level and features an easy way to implement RADIUS in the cloud.

What Is RADIUS Authentication?

RADIUS authentication is a network access control mechanism that uses the RADIUS protocol to verify users and devices before granting network access. A RADIUS server receives authentication requests from network devices such as Wi-Fi access points, switches, and virtual private network (VPN) gateways, verifies the identity against an identity source, and returns an access decision.

RADIUS centralizes authentication and authorization, but the network device still enforces the access decision.

RADIUS provides centralized authentication, authorization, and accounting (AAA) for network access. It can authenticate users with passwords or digital certificates and connect to identity sources such as Active Directory (AD), Lightweight Directory Access Protocol (LDAP) directories, structured query language (SQL) databases, and identity providers.

RADIUS is commonly used for 802.1X network authentication, enterprise Wi-Fi, wired network access, VPNs, and other services that need centralized access control. It supports authentication methods including PAP, MS-CHAPv2, PEAP, EAP-TTLS, and EAP-TLS.

How Does RADIUS Authentication Work?

RADIUS authentication follows a request-and-response model between the RADIUS client, RADIUS server, and an identity source.

When a user or device attempts to connect, the authenticator, such as a wireless access point or network switch, sends a RADIUS authentication request to the RADIUS server. The server verifies the identity, evaluates access policies, and returns a decision. The network device then enforces that decision.

See the diagram below for a visual depiction of how the process works:

Diagram illustrating how RADIUS authentication works with SecureW2

Step 1: Client Sends an Access-Request

A user or device initiates a network connection, such as joining a Wi-Fi network or connecting to a VPN. In an 802.1X deployment, the access point or switch acts as the RADIUS client and sends an Access-Request to the RADIUS server

Common RADIUS clients include wireless access points, network switches, VPN gateways, or other network access servers (NAS).

Step 2: RADIUS Server Validates and Processes the Request

The RADIUS server first validates that the request is coming from a configured RADIUS client and verifies the request’s integrity using the shared secret and applicable message authenticators. It then determines how to process the authentication request based on the configured authentication method.

Depending on the deployment, authentication may use a method such as PAP or MS-CHAPv2, or an Extensible Authentication Protocol (EAP) method such as PEAP, EAP-TTLS, or EAP-TLS.

Step 3: RADIUS Server Verifies the User’s or Device’s Identity

The RADIUS server verifies the credentials or other identity information provided during authentication. Depending on the deployment, it may check an identity source such as Active Directory, an LDAP directory, an SQL database, or a cloud identity provider.

With EAP-TLS, the server validates the client certificate, including its trust chain and applicable certificate requirements. The server may also check the certificate’s identity against an identity source or access policy.

Step 4: RADIUS Server Applies Access Policies

After successful authentication, the RADIUS server evaluates access policies to determine what network access the user or device should receive. Policies can consider factors such as user or device identity, group membership, certificate properties, and network location.

Based on these policies, the server may assign access attributes, such as a virtual local area network (VLAN), or apply other authorization rules that determine the level of access granted.

Step 5: RADIUS Server Returns the Access Decision

The RADIUS server sends a response to the RADIUS client:

  • Access-Accept: Authentication and applicable access policies allow the connection. The network device can grant access and apply any returned access attributes.
  • Access-Reject: The server denies the authentication request, so the network device does not grant access.
  • Access-Challenge: The server requires additional information or authentication steps before making a final decision. The client and server continue the exchange until the server returns a final response.

This process centralizes authentication and access policy decisions while leaving the network device responsible for enforcing the server’s decision.

What Are the Components of RADIUS Authentication?

The components involved in RADIUS authentication depend on how RADIUS is deployed. In a typical 802.1X network, the main components are:

  • Supplicant: The user’s device, such as a laptop, phone, or other endpoint, that requests network access and participates in the authentication process.
  • Authenticator / RADIUS client: The network device that controls access and communicates with the RADIUS server. This is typically a wireless access point or network switch in an 802.1X deployment. In other environments, such as VPNs, the RADIUS client may be a VPN gateway or another NAS.
  • RADIUS server: Processes authentication requests, communicates with an identity source when needed, and applies authentication and authorization policies to determine what access should be granted.
  • Identity source: Provides identity information used for authentication or authorization. Depending on the deployment, this may be Active Directory, an LDAP directory, an SQL database, or a cloud identity provider. Certificate-based authentication may also rely on a certificate authority and certificate properties.

What Is RADIUS Authentication Used For?

RADIUS authentication is used to centralize network authentication and enforce access policies across different network environments.

  • Enterprise Wi-Fi authentication uses RADIUS with 802.1X to authenticate users and devices without relying on a shared Wi-Fi password.
  • Wired network authentication uses RADIUS to control which users and devices can connect to Ethernet ports on managed switches.
  • VPN authentication uses RADIUS to verify users before allowing remote access to the network.
  • Certificate-based authentication uses RADIUS with EAP-TLS to authenticate managed devices using X.509 certificates instead of passwords.
  • Network access control (NAC) uses RADIUS attributes such as user identity, group, device, or certificate properties to assign VLANs and enforce access policies.
  • Centralized authentication connects network infrastructure to identity sources such as Active Directory, LDAP directories, SQL databases, and cloud identity providers.
[sw2_cta type=”tofu” /]

What Is AAA in RADIUS?

AAA stands for authentication, authorization, and accounting. These three functions allow a RADIUS server to verify identities, determine what network access they should receive, and record authentication and session activity.

Authentication

Authentication verifies the identity of a user or device requesting network access. The RADIUS server typically validates credentials, such as a username and password or a digital certificate, against a configured identity source such as Active Directory, Okta, Google, or an LDAP directory.

Authorization

Authorization determines what an authenticated user or device is allowed to access. RADIUS applies network policies based on attributes such as user identity, group, device, or certificate properties. These policies can control access levels, assign VLANs, or restrict access to specific network resources.

Accounting

Accounting records network authentication and session activity. RADIUS can log events such as when a user connects or disconnects, session duration, and data usage. These records help administrators monitor network access, troubleshoot authentication issues, and investigate unusual activity.

How to Set Up a RADIUS Server

A basic RADIUS deployment involves installing the RADIUS server, defining RADIUS clients, configuring an identity source, setting authentication policies, and connecting the network device. The exact configuration depends on the RADIUS implementation and authentication method.

The following example uses FreeRADIUS on Ubuntu or Debian as a basic starting point.

1. Install FreeRADIUS

On Ubuntu/Debian, install FreeRADIUS and its utilities:


sudo apt update
sudo apt install freeradius freeradius-utils

Check that the service is running:

sudo systemctl status freeradius

2. Add the RADIUS Client

Define the access point, switch, or VPN gateway, or other RADIUS client in the FreeRADIUS clients configuration:


client network_device {
    ipaddr = 192.168.1.10
    secret = your_shared_secret
}

The shared secret must match the value configured on the RADIUS client.

3. Configure the Identity Source

Connect FreeRADIUS to the backend used for authentication, such as Active Directory, LDAP, SQL, or another identity provider.

For a basic local test, FreeRADIUS can use its local users file:

testuser Cleartext-Password := "password123"

Production deployments typically use an external identity source rather than storing user credentials locally.

4. Configure Authentication

Enable and configure the authentication method required by the network, such as PEAP, EAP-TTLS, or EAP-TLS. Certificate-based authentication requires the RADIUS server to be configured with the appropriate trusted CA and server certificate.

5. Connect the Network Device

Configure the switch, access point, VPN gateway, or other RADIUS client with the settings required by the deployment, including:

  • RADIUS server IP address
  • Authentication port, typically UDP 1812
  • Accounting port, typically UDP 1813
  • Shared secret
  • Required 802.1X and EAP settings

6. Test the Configuration

Run FreeRADIUS in debug mode to view authentication requests and troubleshoot configuration issues:

sudo freeradius -X

For a basic username-and-password test, you can use radtest:

radtest testuser password123 127.0.0.1 0 testing123

A successful radtest authentication should return an Access-Accept response. This test verifies basic RADIUS credential authentication; testing EAP methods such as PEAP, EAP-TTLS, or EAP-TLS requires an appropriate supplicant and network configuration.

Is RADIUS UDP or TCP?

RADIUS traditionally uses User Datagram Protocol (UDP) for authentication and accounting, typically on UDP ports 1812 and 1813.

To understand why RADIUS uses UDP, it helps to distinguish between UDP and Transmission Control Protocol (TCP), the two main transport-layer protocols used for network communication.

  • UDP is connectionless and lightweight, with no built-in guarantee that packets will arrive or arrive in order.
  • TCP is connection-oriented and provides reliable, ordered delivery of data between endpoints.
RADIUS traditionally uses UDP because its request-response model handles retransmissions at the RADIUS protocol level, avoiding the connection overhead of TCP. RADIUS authentication uses UDP 1812, while RADIUS accounting typically uses UDP 1813.

Newer RADIUS transport options also exist, including RADIUS over TCP and RADIUS over TLS (RadSec), which provide reliable or encrypted transport when required.

Does RADIUS Use LDAP?

Yes, RADIUS can use LDAP to communicate with servers designed for LDAP communication. Active Directory is a widely-used platform that uses LDAP for authentication purposes. However, AD is notorious for its lack of flexibility when it comes to cloud computing services. JoinNow Cloud RADIUS makes it easy for AD-domain admins to bridge the gap from on-prem to cloud.

LDAP is not the only protocol RADIUS can use to communicate with directories. Security Assertion Markup Language (SAML) is another protocol that RADIUS is capable of using. Let’s take a look at the differences between the two.

RADIUS Authentication: LDAP vs. SAML

The biggest difference between LDAP and SAML is what each protocol does. LDAP is a directory access protocol used to look up and authenticate identities held in a directory, most often one the organization runs itself. SAML is a federation standard that passes signed authentication assertions between an identity provider and the service a user is trying to reach.

As organizations move more of their computing to the cloud, federation protocols such as SAML and OpenID Connect are the ones cloud identity providers expose, while LDAP remains common for on-premises directories.

Microsoft Entra ID (formerly Azure AD) supports SAML alongside OpenID Connect and OAuth 2.0, as do other cloud directories like Google and Okta. Microsoft’s own guidance is to choose OpenID Connect and OAuth 2.0 where an application supports them, and SAML for existing applications that do not.

Cloud RADIUS can be configured with either SAML or LDAP, which means it can seamlessly integrate with your on-prem or cloud network — or even a hybrid environment.

How Does RADIUS Work With 802.1X?

802.1X controls network access, while RADIUS performs the backend authentication and authorization. When a device tries to connect:

  • 802.1X establishes the authentication process between the device and the network, while the authenticator, such as a switch or access point, forwards the authentication requests to the RADIUS server.
  • The RADIUS server validates the user’s or device’s credentials or certificate against an identity source such as Active Directory, Okta, Google, or LDAP directories.
  • The RADIUS server can use attributes such as user roles or group membership to apply network policies.
  • The RADIUS server returns the authentication decision, and the 802.1X authenticator enforces it by allowing or denying network access.
802.1X provides the network access control framework, while RADIUS provides the centralized authentication, authorization, and policy decision-making behind it.

RADIUS Authentication Protocols

RADIUS supports several authentication protocols, each suited to different network environments and authentication requirements. The table below outlines the most common protocols and how they work with RADIUS.

Protocol

Authentication type

How it works

Key security consideration

EAP-TTLS/PAP

Credentials

Creates an encrypted tunnel between the client and server, then uses PAP to transmit the user’s credentials within the tunnel.

Relies on password-based authentication and proper server validation; weak configurations can expose credentials to credential theft and man-in-the-middle attacks.

PEAP-MSCHAPv2

Credentials

Creates a protected TLS tunnel and uses MS-CHAPv2 for username and password authentication, commonly in Windows and Active Directory environments.

Password-based authentication remains vulnerable to credential theft if the protocol or server validation is misconfigured or exploited.

EAP-TLS

X.509 certificates

Uses client and server certificates to mutually authenticate the endpoint and RADIUS server.

Provides strong certificate-based authentication and eliminates the need to transmit user passwords, reducing the risk of credential theft.

Authenticating With Cloud RADIUS and Digital Certificates

EAP-TLS uses digital certificates to authenticate devices and the RADIUS server without requiring users to enter passwords. To deploy EAP-TLS, organizations need a public key infrastructure (PKI) to issue, distribute, validate, and manage the X.509 certificates used for authentication.

During authentication, the client device proves that it has the private key associated with its certificate, while the RADIUS server validates the certificate against the organization’s trust requirements. The private key never leaves the device. This helps prevent credentials such as passwords from being exposed or reused during network authentication.

Certificate-based authentication can also simplify the user experience. Once a device has been provisioned with the appropriate certificate and network configuration, it can authenticate automatically without requiring the user to enter a password. Administrators can also use certificate properties and other identity information as part of access policies.

Cloud RADIUS can provide the RADIUS authentication service, while a managed PKI handles the certificate lifecycle.

[sw2_cta type=”bofu” /]

The Benefits of Cloud RADIUS Solutions

A traditional on-premises RADIUS deployment requires organizations to provision and maintain the RADIUS infrastructure themselves. A cloud-based RADIUS service moves that infrastructure to a hosted environment, reducing the amount of server management required from the organization’s IT team.

Cloud-based RADIUS solutions can provide several practical benefits:

  • Less infrastructure to manage: Organizations do not need to maintain dedicated RADIUS servers on-site or manage the underlying server infrastructure themselves.
  • Centralized authentication: A cloud RADIUS service can provide a central point for authenticating users and devices across network access environments such as Wi-Fi, wired networks, and VPNs.
  • Integration with identity systems: Cloud RADIUS can connect to identity sources such as Microsoft Entra ID, Active Directory, LDAP directories, or other supported identity providers, depending on the service and deployment.
  • Policy-based access: RADIUS can use identity, group membership, certificate information, and other attributes to determine which network access policies apply to a user or device.
  • Support for distributed environments: Because the RADIUS service is hosted in the cloud, it can support organizations with users, devices, and network infrastructure spread across multiple locations without requiring a RADIUS server at each site.

The specific benefits and integrations available depend on the cloud RADIUS provider and the organization’s network and identity architecture.

Securely Authenticate Users With JoinNow Cloud RADIUS

RADIUS provides the authentication and authorization infrastructure behind secure network access for Wi-Fi, wired networks, VPNs, and other environments. For organizations using EAP-TLS, combining JoinNow Cloud RADIUS with certificate-based authentication can simplify deployment while reducing the need for password-based authentication.

Cloud RADIUS works with JoinNow Dynamic PKI to support X.509 certificate authentication and 802.1X deployments. The cloud-based service provides the RADIUS infrastructure, while Dynamic PKI handles certificate issuance and management, giving organizations the components they need to implement certificate-based network authentication.

Explore SecureW2 Cloud RADIUS pricing or schedule a demo to see the available solutions and find the right option for your organization.

Frequently Asked Questions

Is RADIUS authentication secure?

RADIUS authentication can be secure when configured with strong authentication methods and proper network controls. EAP-TLS provides certificate-based authentication and avoids password-based credential theft, while protocols such as PEAP-MSCHAPv2 and EAP-TTLS/PAP rely on passwords. Security also depends on factors such as certificate validation, shared-secret protection, server configuration, and network segmentation.

Does RADIUS require 802.1X?

No, RADIUS does not require 802.1X. RADIUS is an authentication, authorization, and accounting protocol that can support several network access scenarios, including VPNs, network devices, and 802.1X authentication. When used with 802.1X, RADIUS typically handles the backend authentication while the switch or access point acts as the authenticator.

What is the default RADIUS authentication port?

RADIUS authentication typically uses UDP port 1812, while RADIUS accounting typically uses UDP port 1813. Older RADIUS implementations may use UDP ports 1645 for authentication and 1646 for accounting.

What is the difference between RADIUS and LDAP?

RADIUS handles network authentication and access control, while LDAP is primarily a directory protocol used to access identity information. RADIUS can use an LDAP directory as an identity backend, allowing the RADIUS server to authenticate users against identities stored in LDAP. In practice, LDAP stores and provides identity data, while RADIUS applies network authentication and access policies.

What is the difference between RADIUS and TACACS+?

RADIUS and TACACS+ both provide centralized AAA, but they are commonly used for different network access requirements. RADIUS is widely used for user and device network access, including Wi-Fi, 802.1X, and VPNs. TACACS+ is commonly used for administrative access to network infrastructure and separates authentication, authorization, and accounting more distinctly.

Which RADIUS authentication method is most secure?

EAP-TLS is generally considered the strongest commonly used RADIUS authentication method because it uses X.509 certificates instead of passwords. It provides mutual authentication between the client and server and removes the need to transmit or validate user passwords. Its security still depends on proper PKI, certificate validation, certificate lifecycle management, and secure RADIUS configuration.

What happens when a RADIUS server is unavailable?

When a RADIUS server is unavailable, the network device cannot complete normal RADIUS authentication and may deny new access attempts. The exact behavior depends on the network device and its configured failover or fallback options. Organizations can use multiple RADIUS servers, load balancing, or local authentication as appropriate to maintain availability when a primary RADIUS server fails.

Neha Singh

Neha Singh is a CISSP, with 13 years of experience, specializing in PKI, RADIUS, and 802.1X frameworks. She is skilled at translating real-world customer challenges into practical scalable solutions. Neha drives adoption of complex security solutions through clear, cross-functional collaboration with Product, Engineering, and Sales. Combines her deep product management experience with a research-driven mindset to build customer trust. She holds multiple industry certifications and serves on the Board of Directors for the ISC2 Chennai Chapter.

Related Posts