RADIUS
RADIUS (Remote Authentication Dial-In User Service) is a networking protocol that provides centralized Authentication, Authorization, and Accounting (AAA) for users connecting to network services.
What is RADIUS?
RADIUS (Remote Authentication Dial-In User Service) is a client-server protocol that centralizes authentication, authorization, and accounting (AAA) for network access. A RADIUS client (typically a network access server, VPN gateway, or Wi-Fi controller) forwards user credentials to a RADIUS server, which validates them against its user database or an external identity source (LDAP, Active Directory, etc.).
RADIUS supports multiple authentication methods including PAP, CHAP, MS-CHAPv2, and EAP (Extensible Authentication Protocol). EAP allows RADIUS to integrate with more secure authentication mechanisms like TLS certificates, token cards, and biometrics. The protocol uses UDP as its transport layer, with ports 1812 for authentication/authorization and 1813 for accounting.
While RADIUS is an older protocol, it remains widely deployed for network infrastructure authentication — including enterprise Wi-Fi (802.1X), VPN gateways, DSL/cable broadband, and network device administration. It is valued for its simplicity, broad vendor support, and ability to proxy requests between multiple RADIUS servers in hierarchical deployments.
Analogy
RADIUS is like a hotel's front desk for the network. When a guest wants to enter their room, they don't deal with each door individually — they check in at the front desk (RADIUS server), get verified, and are granted access to their specific room (network resource). The front desk also logs who came and went (accounting).
Types and Use Cases
- Enterprise Wi-Fi Security: RADIUS authenticates users connecting to corporate Wi-Fi using WPA2/3-Enterprise with 802.1X and EAP-TLS or PEAP.
- VPN Access: Remote employees authenticate via RADIUS when connecting through IPSec or SSL VPN gateways.
- Network Device Administration: Switches, routers, and firewalls use RADIUS for administrative login (SSH/HTTPS) authentication and command authorization.
- ISP Broadband: Internet service providers use RADIUS to authenticate dial-up, DSL, and fiber broadband subscribers and track usage for billing.
How it Works
{
"radiusRequest": {
"type": "Access-Request",
"code": 1,
"attributes": {
"User-Name": "jane.doe@example.com",
"User-Password": "[encrypted]",
"NAS-IP-Address": "192.168.1.1",
"NAS-Port": 10,
"Service-Type": "Framed-User",
"Called-Station-Id": "00:11:22:33:44:55",
"Calling-Station-Id": "AA:BB:CC:DD:EE:FF"
}
},
"radiusResponse": {
"type": "Access-Accept",
"code": 2,
"attributes": {
"Framed-IP-Address": "10.0.0.42",
"Session-Timeout": 28800,
"Idle-Timeout": 1800,
"Filter-Id": "corporate-wifi-acl"
}
}
}RADIUS vs LDAP
RADIUS
LDAP
RADIUS is an AAA protocol for network access control,
LDAP is a directory access protocol for reading and writing directory information (user records, attributes).
RADIUS typically handles authentication for network devices (Wi-Fi, VPN),
LDAP serves as a central user repository that RADIUS can query.
RADIUS supports accounting (session tracking, data usage),
LDAP does not have built-in accounting capabilities.
Best Practices for RADIUS
- Use EAP-TLS or EAP-TTLS with certificate-based authentication instead of PAP or CHAP for stronger security in wireless deployments.
- Cluster RADIUS servers with failover and load balancing to ensure high availability for network authentication.
- Protect the RADIUS shared secret (used between client and server) and rotate it periodically.
- Monitor RADIUS accounting logs for anomalous usage patterns that might indicate compromised credentials or devices.
How LoginRadius Powers RADIUS
LoginRadius supports integration with RADIUS deployments through LDAP directory synchronization and SAML federation. Organizations can use LoginRadius as the central identity provider while RADIUS servers authenticate users against the LoginRadius directory for network access (Wi-Fi, VPN). This enables centralized identity management across both web applications and network infrastructure.
FAQs
Yes. While SAML and OIDC are used for web application SSO, RADIUS remains the standard for network infrastructure authentication (Wi-Fi, VPN, switches). Modern deployments often bridge the two by using RADIUS servers that integrate with SAML/OIDC identity providers.
Diameter is the successor to RADIUS, offering improved reliability (TCP/SCTP instead of UDP), better error handling, and support for mobile network protocols (4G/5G). However, RADIUS remains more widely deployed in enterprise networks due to its simplicity.
LoginRadius can integrate with RADIUS infrastructure through its identity federation capabilities. A RADIUS server can be configured to authenticate against LoginRadius via LDAP or SAML bridging, enabling organizations to use LoginRadius as the identity source for network access while maintaining their existing RADIUS infrastructure.