How a RADIUS Server Controls Corporate Wi-Fi Access

A shared Wi-Fi password gives everyone who knows it the same basic credential. An 802.1X network can instead evaluate an individual user or device when it connects. A server using RADIUS centralizes that decision, allowing the organization to apply access policy and record session events across many access points.

Trace a connection request

In an enterprise Wi-Fi deployment, the laptop or phone acts as the 802.1X supplicant. The access point or wireless controller acts as the authenticator and RADIUS client: it receives the connection attempt and sends an Access-Request to the RADIUS server. The device being connected is not itself the RADIUS client in this exchange. Microsoft’s client overview describes the access device’s role.

The authentication exchange may involve several messages rather than one password check. An Extensible Authentication Protocol (EAP) method carries the information needed for the chosen authentication process. For example, with certificate-based authentication, the server evaluates the presented client certificate against its configured trust and policy; the device also validates the server certificate according to its profile. The precise identity checks depend on the method and deployment.

A RADIUS authentication server may consult a directory, certificate infrastructure, or another identity source and then evaluate policy conditions such as group membership or device status. If authentication and authorization succeed, it sends Access-Accept, potentially with attributes the access device uses to place the session in an appropriate VLAN or apply another supported policy. If the request fails, it sends Access-Reject. An Access-Challenge may be part of the exchange before a final decision.

Account for the session

The access device enforces the response and, when accounting is configured, can send session start, stop, and periodic update records. These can identify the user or device, access point, session time, and other available attributes. The organization’s logging system can use them to investigate a connection or reconcile usage. Accounting depends on configuration and delivery; a successful authentication does not prove every later session record was received.

A RADIUS server is therefore one part of the access path. The wireless profile, authenticator, identity source, policy, and logging destination must also work. The server handling RADIUS authentication can deny a valid credential if the matching policy does not authorize the request. Even after acceptance, access can fail if the device cannot apply the returned attributes.

Test the integration and resilience

Before rollout, register each access point or controller as an authorized client on the RADIUS service, using the correct source address and matching shared secret. Check routing and firewall rules for the authentication and accounting ports configured at both ends. Verify the EAP method, server certificate trust, identity-source reachability, policy order, and any VLAN or role mapping supported by the wireless equipment.

Test an authorized connection and a controlled denial. Confirm the decision in the access device and server logs, then check that accounting records reach their destination. Record timestamps and a session identifier so the events can be correlated without placing credentials in tickets or logs. Test from representative device types and locations, including a site reached over a remote link.

For availability, configure a secondary server for RADIUS requests where the equipment supports it, and confirm that policies, identity access, certificates, client definitions, and accounting settings are consistent. Test failover by making the primary unavailable in a planned window. Measure the delay before a new connection succeeds and verify the recovery path; an existing session and a new authentication may behave differently during an outage.

Diagnose a common failure

If devices associate with Wi-Fi but repeatedly fail to authenticate, compare the access point’s request time with the logs of the server running RADIUS. No corresponding request points toward the configured server address, network path, or client registration; a logged rejection provides a reason or policy match to investigate next.