Whenever large companies need network authentication, RADIUS (RFC 2865) is the protocol of choice. RADIUS is an AAA protocol which stands for authentication, authorization and accounting. It is therefore best suited for controlling access to networks like Wi-Fi, Wired (802.1X, EAP) or VPN. The protocol was developed by Livingston Enterprises, Inc. in 1991 and is now part of the IETF standards.
RADIUS is an efficient protocol for authentication purposes that uses the UDP transport protocol. Nonetheless, some traffic will not be encrypted during transport. This can be avoided by using RadSec (RFC 6614) which is transported over TCP and completely encapsulated within a TLS tunnel.
The easiest way to push device or user certificates to your clients is SCEPman, as it is super-easy to deploy and integrates seamlessly with Intune. You can also use your own on-premise PKI.
RADIUSaaS supports multiple CAs in parallel.
To proof revocation of certificates, our RADIUSaaS leverages OSCP.
A Certificate Revocation List (CRL) is currently not supported.
Each customer has access to their own personal instance through their own Admin Portal, which can be used for tasks such as creating users, changing your allowed certificates, adding proxies or viewing server logs.
Our RADIUS server only allows RadSec connections. If your WiFi infrastructure does not support RadSec, our RADIUSaaS features a proxy functionality, which will establish a secure tunnel allowing you to use our service with traditional UDP.
Some of your devices may not able to receive certificates. Reasons could be that they are not managed by any policy provider or they simply are technically not able to work with certificates. In those cases or guests scenarios, you can add users to your instance and restrict the access to a specific time frame if needed. This allows you to authenticate printers, TV's or other devices with the same instance.
Please follow the steps on the following page to get your clients ready authenticating with RADIUS-as-a-Service!