When it comes to authorizing network access, very few protocols are more widely used than RADIUS (Remote Authentication Dial In User Service). The RADIUS protocol<\/a> was originally created for controlling on-prem dial-up internet access and accounting management.<\/p>\n\n\n\n
RADIUS is a network authentication protocol that is used to provide secure access to wireless networks by requiring each user to authenticate their identity by leveraging core user credentials. These credentials are stored within an identity provider<\/a> (IdP), also known as a directory service, which acts as the source of truth for authenticating user identities. <\/p>\n\n\n\n
The primary benefit of RADIUS authentication is enhanced WiFi security<\/a> – rather than using a shared SSID and password, each user logs in with their own unique set of secure credentials. This more secure approach to network access is just as user friendly, if not moreso, because each user knows their credentials off the top of their head. <\/p>\n\n\n\n
Of course, implementing RADIUS has certain challenges in and of itself. Traditional RADIUS solutions are on-prem implementations that require heavy investment into on-prem identity management infrastructure. Not only do IT organizations need a dedicated RADIUS server, but they also need an existing identity management infrastructure to integrate with. Then, the challenge becomes integrating the RADIUS server throughout an environment, not to mention ongoing maintenance. <\/p>\n\n\n\n
The choice in IdP can impact the end result as well. Active Directory (AD), for example, is basically limited to on-prem networks of Windows-based IT resources. Consequently, IT organizations may require additional solutions to extend RADIUS functionality to non-Windows resources, which doesn\u2019t make sense in modern IT environments that contain a mix of device and resource types.<\/p>\n\n\n\n