# General ## Authentication #### 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](https://portal.azure.com/) account 2. Go to **Microsoft Entra ID** 3. Select **Enterprise applications** 4. Click **+ New Application**

Showing creation of a new application

5. Click **+ Create your own application** 6. Give a name for the app (e.g. RADIUSaaS Portal) 7. Choose **Integrate any other application you don’t find in the gallery** and 8. 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

Click "User and groups"

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

Click "Properties"

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

Click Single Sign-on - Select "Linked" mode

Enter your RADIUSaaS instance URL

Enter your RADIUSaaS instance URL

**Access My Apps** Your users should now be able to access the newly created link tile via [My Apps](https://myapps.microsoft.com/). ## RADIUS Return Attributes #### Which VLAN-related attributes does RADIUSaaS return by default? {% hint style="info" %} In case you require other VLAN attributes than returned by default, please [contact our support](https://www.radius-as-a-service.com/help/). {% endhint %} If VLAN tagging is enabled by configuring and enabling a relevant [Rule](/admin-portal/settings/rules.md#vlan-assignment), RADIUSaaS returns the following generic VLAN attributes `"Tunnel-Type": "VLAN"` `"Tunnel-Medium-Type": "802"` `"Tunnel-Private-Group-ID"` along with the other commonly used vendor-specific VLAN attributes: `"WiMAX-VLAN-ID"` `"Nexans-Port-Default-VLAN-ID"` `"Dlink-VLAN-ID"` `"UTStarcom-VLAN-ID"` `"DHCP-IEEE-802.1Q-VLAN-ID"` `"Motorola-WiMAX-VLAN-ID"` `"Telrad-C-VLAN-ID"` `"Telrad-S-VLAN-ID"` `"SN-Assigned-VLAN-ID"` `"Extreme-VM-VLAN-ID"` `"Ruckus-VLAN-ID"` `"Mikrotik-Wireless-VLANID"` `"Egress-VLANID"` `"HP-Egress-VLANID"` ## 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](/admin-portal/settings/settings-server.md#properties). **RadSec Connection** Since the RadSec servers are independent of 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 timeout15 s
EAP max retries5
EAP identity timeout10 s
EAP identity retries5
EAPOL key timeout2000 ms
EAPOL key retries4
## Logs #### How can I identify the public IP address of the site from which an authentication originates? To identify the public IP 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 relevant 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 public IP can be extracted from the **message > Packet-Src-IP-Address** property of the log entry.
**RADIUS Connection** * Navigate to **Insights > Logs**. * Configure the relevant time range / search window. * Set the **Log-type** filter to the **proxy**. * Identify the relevant authentication (by correlating the timestamp and username). * The public IP can be extracted from the **message** property of the log entry:
## Does RADIUSaaS support WPA3 Enterprise? Yes, RADIUSaaS supports WPA3 Enterprise. It also supports WPA3 Enterprise 192-bit mode with the following limitation: **Windows 11 24H2** introduced stricter certificate requirements for WPA3-Enterprise 192-bit encryption, leading to authentication failures if the entire certificate chain does not meet specific cryptographic strength standards. This update mandates RSA key lengths of at least 3072-bits or ECDSA with the P-384 curve for all certificates involved in the authentication process. Organizations using certificates with weaker parameters, such as RSA 2048-bit, may encounter issues. While SCEPman supports 4096-bit RSA keys for Windows, this is limited to the Software Key Storage Provider (KSP), as the hardware TPM does not support this key size. If after upgrading to Windows 11 24H2 you experience authentication issues, look for "SEC\_E\_ALGORITHM\_MISMATCH" errors in the Event Viewer (System Logs and CAPI2) as an indicator for incompatibility in the cryptographic algorithms between the client and the server. ### What can I do if I want to use WPA3-Enterprise authentication on Windows? Your current option moving forward is to address the certificate requirements for WPA3-Enterprise 192-bit on your Windows 11 24H2 clients. This includes updating the Leaf Certificate to meet the new minimum requirements. Please note that Intune does not currently include an option in its SCEP profile to specify a key size of 3072-bits which could be stored in the Trusted Platform Module (TPM) of the receiving computer. Due to this limitation, currently the only feasible solution for Windows clients is to use 4096-bit RSA key enrolled in Software Key Storage Provider (KSP). {% hint style="success" %} As Intune's WiFi profile only provides WPA2-Enterprise you will need to use an external tool to create a WPA3-Enterprise WiFi profile. For convenience, RADIUSaaS includes this tool [here](https://docs.radiusaas.com/admin-portal/settings/trusted-roots#xml). {% endhint %} ## Identity Providers ### **Does RADIUSaaS support Okta as an identity provider?** * **Yes** for admin & users login to the web-console * **No** for authentication via the RADIUS protocol #### **User and admin Portal (web-console) login** Okta is fully supported as an identity provider for signing in to the RADIUSaaS Web Portal. RADIUSaaS does not maintain its own administrator identities and instead delegates authentication to your existing identity provider, so administrators, viewers, and invited users can log in with their Okta accounts. Okta is integrated through the **Custom OIDC Provider** option in the [Permissions](/admin-portal/settings/permissions.md#custom-oidc-provider-okta) section. Step-by-step setup instructions, including the required redirect URI, authentication and token URLs, client ID, client secret, and `openid email` scope, are documented in the [Permissions](/admin-portal/settings/permissions.md#overview) article. #### **RADIUS protocol authentication (Wi-Fi, wired 802.1X, VPN)** Okta is **not** supported as an identity provider for authentication that takes place over the RADIUS protocol. As described in the [Users](/admin-portal/users.md) section, RADIUSaaS does not integrate with any external IDP for username/password-based network authentication. All username/password accounts used for RADIUS authentication must be created and managed directly in the RADIUSaaS Admin Portal. {% hint style="info" %} For RADIUS-based network authentication, we generally recommend **against** username/password approaches that rely on an external identity provider. Such setups require credentials to be transmitted or relayed during the network authentication and broaden the attack surface in ways we consider a relevant security risk. Wherever possible, use **certificate-based authentication** (EAP-TLS) instead. For background and a detailed explanation of the risks of password-based network authentication, see [Certificate-Based Network Authentication](https://www.scepman.com/certificate-network-authentication/). {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.radiusaas.com/other/faqs/general.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.