The service state of your RADIUSaaS instance is available under https://YOURNAME.radius-as-a-service.com

The RADIUSaaS homepage presents you with an interactive service state that is updated in real-time.

Service State

Health State

When you access the homepage of your RADIUSaaS instance, the health state of the service including its key components, i.e. RADIUS proxies and RadSec servers (the core service), is illustrated. The availability of the individual components is monitored in real-time and realized through actual authentications (PAP-based) that are periodically performed. By hovering over individual nodes, additional information such as the public IP address and the data center location is shown.

In case, a node is detected to be malfunctioning, the corresponding node along with the no longer available authentication and communication path is highlighted in red:

Important: As long as there is at least one green path leading to Authentications, the service is generally available. In case you are using RADIUS proxies, ensure that you have followed our architectural recommendations to decrease the likelyhood that a proxy failure leads to an overall outtage of the service.

Configuration State

The configuration of your RADIUSaaS instance may at times be rather complex, especially in cases where the Rule Engine is heavily used. To still provide you with an easy overview, RADIUSaaS offers a tree view of all active configurations. The view can be reached by clicking on the Authentications node in the Health State view. A tree view of all configured rules will unfold.

On the first layer of the tree, the network types are presented (WiFi, Wired, VPN). On subsequent layers the structure and configuration of the rules is shown, including permitted authentication types (certificate-based, username/password-based), trusted CAs, allow-listed APs/switches and SSIDs, and finally RADIUS return attributes such as VLAN- or other tags - if any. Grayed-out rules are disabled and thus will lead to rejected authentications in case none of the active/green rule-paths are fulfilled for a particular network type during authentication.

Last updated