A RADIUS server authenticates and authorizes users and devices accessing a network, enforcing access policies through centralized credentials checking. It acts as a gatekeeper for Wi-Fi, VPNs, and dial-up connections by validating login attempts and assigning permissions based on predefined rules.
RADIUS-Remote Authentication Dial-In User Service-is a client-server protocol that runs over UDP. When a user tries to connect to a network, their device sends login details to a network access server (NAS), which forwards the request to the RADIUS server. The server checks the credentials against a database, then returns an approval or denial. If approved, it may also send configuration settings such as IP address assignment or bandwidth limits.
The protocol was standardized in RFC 2865 (1999) and remains widely used in enterprise, educational, and service provider networks. Major vendors like Cisco, Juniper, and Microsoft integrate RADIUS into their networking hardware and software. According to the Internet Engineering Task Force (IETF), RADIUS provides a foundation for scalable, secure access control across large-scale environments.
When a user connects to a secured Wi-Fi network, their device sends a username and password to the access point. The access point, acting as the RADIUS client, forwards the request to the RADIUS server using UDP port 1812 for authentication and port 1813 for accounting.
The RADIUS server validates the credentials against a backend directory-such as Active Directory, LDAP, or a local database. If valid, it responds with an "Access-Accept" message containing session parameters. If invalid, it sends "Access-Reject." During the session, the server logs usage via RADIUS Accounting messages sent to port 1813.
For example, a university student logging into the campus Wi-Fi enters their NetID and password. The access point forwards the request to the central RADIUS server. The server verifies the credentials against the university's identity management system. Upon success, it grants internet access and assigns a temporary IP address via DHCP, which is coordinated through the RADIUS response.
RADIUS servers require three core elements: authentication database, policy engine, and communication interface. The authentication database stores user accounts and secrets. The policy engine enforces rules-like time-of-day restrictions or multi-factor authentication requirements. The interface handles incoming requests and responses using encrypted packets.
Common RADIUS server implementations include FreeRADIUS (open-source), Microsoft NPS (Network Policy Server), and Cisco ISE (Identity Services Engine). These platforms support various authentication methods:
| Method | Description | Use Case |
|---|---|---|
| PAP | Plain-text password transfer | Legacy systems; not recommended due to exposure risk |
| CHAP | Password transmitted as hash | Older dial-up and PPP connections |
| EAP-MD5 | Challenge-response with MD5 hashing | Basic Wi-Fi authentication in older networks |
| EAP-TLS | Certificate-based mutual authentication | Enterprise-grade Wi-Fi (WPA2-Enterprise) |
Modern deployments favor EAP-TLS because it prevents man-in-the-middle attacks. A hospital using WPA2-Enterprise Wi-Fi requires staff to present a digital certificate issued by the organization's internal CA. The RADIUS server validates both the certificate and the user's identity before granting access.
Enterprises use RADIUS to manage access across thousands of endpoints. A multinational corporation with offices in New York, London, and Tokyo uses a single RADIUS server cluster to authenticate employees connecting via corporate VPN. This ensures consistent policies-such as requiring MFA or restricting access to certain departments-regardless of location.
Service providers rely on RADIUS to bill customers for broadband usage. Cable companies assign unique usernames and passwords to each household. When a user logs in, the RADIUS server verifies the account status and tracks data consumption via accounting records. This enables changing bandwidth throttling during peak hours.
Public Wi-Fi hotspots in airports and cafes often use RADIUS to enforce captive portal policies. After connecting, users are redirected to a login page. Their credentials are sent to a RADIUS server hosted by the hotspot provider. Successful authentication unlocks internet access for a set duration or data limit.
RADIUS is not a firewall or encryption tool. It does not protect data in transit-it only validates identities. Data confidentiality must be handled separately via protocols like TLS or IPsec. RADIUS packets are unencrypted by default, making them vulnerable to sniffing if not protected by a tunneling mechanism.
Some confuse RADIUS with TACACS+. While both handle authentication, TACACS+ separates authentication, authorization, and accounting (AAA) into distinct processes and supports more granular command-level access control. TACACS+ is typically used in high-security environments like government agencies or financial institutions.
Another error is assuming RADIUS works without a backend directory. The server cannot validate users unless linked to a database. In practice, RADIUS integrates with Active Directory, OpenLDAP, or custom databases. Without this integration, the server returns "Access-Reject" for every request.
In 2022, Stanford University deployed a RADIUS infrastructure to manage access to its research computing clusters. Over 30,000 students, faculty, and visiting researchers needed authenticated access to high-performance computing resources.
The IT team configured FreeRADIUS to authenticate against Stanford's central LDAP directory. They implemented two-factor authentication using RSA SecurID tokens. Each login attempt required a username, password, and one-time code.
Upon successful validation, the RADIUS server returned an "Access-Accept" packet with a VLAN assignment. Users were placed in a dedicated network segment with restricted outbound traffic. The system logged all sessions and flagged unusual behavior-such as multiple failed attempts from a single IP-for review.
This setup reduced unauthorized access incidents by 92% over six months, according to internal audit reports. The university also saved $180,000 annually by eliminating manual account provisioning and reducing helpdesk tickets related to access issues.
Understanding what is radius server used for reveals its role as a critical component in modern network security. It enables secure, scalable access control across diverse environments-from small businesses to global enterprises. Its integration with identity systems and support for strong authentication methods make it essential for protecting sensitive data and infrastructure.