How often is a device typically authenticating against RADIUSaaS?

This is difficult to answer as it depends on the behavior of your users, clients and networking gear (APs, NACs, switches). Additionally, it is important to note that RADIUSaaS will neither

  • trigger an authentication, nor

  • send a termination request via its accounting port to the client, potentially triggering a re-authentication.

If you feel your devices are authenticating very frequently (multiple times an hour) without the user constantly restarting the client, then this could be for the following reasons:

  • The network controller doesn't authenticate the client fast enough for the client to join the network, so the client attempts to authenticate again. Check the network controller to see if/when it is receiving an answer from RaaS.

  • The network controller is re-initiating authentication. Check the network controller for what might be causing this.

RADIUSaaS Admin Portal

How can I add the RADIUSaaS Admin Portal to My Apps?

Create the App

First you have to create an Enterprise app. To do this via the Azure portal, follow these steps:

  1. Login to your Azure account

  2. Go to Microsoft Entra ID

  3. Select Enterprise applications

  4. Click + New Application

  1. Click + Create your own application

  2. Give a name for the app (e.g. RADIUSaaS Portal)

  3. Choose Integrate any other application you don’t find in the gallery and

  4. Click Create

After that the app is set up, we now need to add users to it and configure the logo and link

Add Users and a Logo

  1. Under Manage go to User and groups - Add all users/groups who should be able to view/use your new URL tile and save

  2. Click Properties - Upload an image logo of your choice and save

  3. Click Single Sign-on - Select Linked mode - Then enter the URL you want and save.

Access My Apps

Your users should now be able to access the newly created link tile via My Apps.

RADIUS Return Attributes

In case you require other VLAN attributes than returned by default, please contact our support.
















Secondary Instance and Failover

How does a secondary instance behave in terms of failover?

A secondary instance means that you have at least a secondary RadSec server that works independently of your main instance but has the same configuration. If you have one, you can see multiple IP Addresses under RadSec IP Addresses.

RadSec Connection

Since the RadSec servers are independent from each other, they will not handle any kind of failover. You should add both IP addresses/DNS entries to your Network controller which decides to which server the authentication requests are forwarded.

RADIUS Connection

With your RADIUS proxies, it's a little different: Your proxies are aware of each of your RadSec instances and their health states and thus will handle failover if the primary server fails.

Timers & Timeouts

What EAP parameters and timeouts should be configured?

Not every access point or switch (authenticator) provides you with the same amount of configuration options for EAP and general (RADIUS server) timeout parameters. Below overview presents the maximum set of parameters known to us and how they should be configured to allow for maximum reliability of the connection between the authenticator and RADIUSaaS.

RADIUS Server Timeout

5 seconds

EAP Parameters

EAP timeout

15 s

EAP max retries


EAP identity timeout

10 s

EAP identity retries


EAPOL key timeout

1000 ms

EAPOL key retries



How can I identify the public IP address (PIP) of the site from which an authentication originates?

To identify the PIP of the authenticating site for a particular authentication, the approach depends on whether you are using a RADIUS connection (via the RADIUS proxies) or a direct RadSec connection:

RadSec Connection

  • Navigate to Insights > Logs

  • Configure the relvant timerange / search window

  • Set the Logtype filter to details

  • Identify the relevant authentication (by correlating the timestamp and username)

  • Identify an ACCESS_REQUEST message (message > Packet-Type = Acess-Request) that belongs to the authentication under investigation

  • Expand the respective log entry

  • The PIP can be extracted from the message > Packet-Src-IP-Address property of the log entry.

RADIUS Connection

  • Navigate to Insights > Logs

  • Configure the relvant timerange / search window

  • Set the Logtype filter to proxy

  • Identify the relevant authentication (by correlating the timestamp and username)

  • The PIP can be extracted from the message property of the log entry:

Last updated