Troubleshooting
Last updated
Last updated
Check that your client has a certificate to authenticate and that you are using the correct WiFi configuration profile or XML.
Check that you've done the following:
Told your RADIUS Server which certificates are allowed to connect as described here
Imported the active RADIUS Server certificate as trusted root on your client as described here
Also check your Logs. There is a detailed description of the error. Maybe it's this issue.
If your Clients need to verify on connecting the first time, and you're seeing this dialog:
Make sure that you have referenced the RADIUS server certificate in your WiFi profile and provided the server certificate's SAN attribute (FQDN) and common name (CN):
If your Logs contain error messages similar to the ones shown below
it can have the following root causes:
Client throws error TLS Alert read:fatal:unknown CA
Your Client doesn't know the Server certificate and rejects the connection. Check that you've added your Server certificate as described here.
You've changed/added a new Server certificate and your XML profile on the client is using the old one. In that case, please double-check that you've either updated your WiFi/Wired profile or re-generated your XML after adding the certificates and pushed that to your clients.
Server throws error TLS Alert write:fatal:unknown CA
Your RADIUS server doesn't know the issuer of the certificate which was used for authentication. Add your CA as described here.
If you use macOS (and possibly other Apple platforms) and if your Logs contain error messages similar to the one shown below
it can have the following root causes:
If your Logs contain error messages similar to the ones shown below
... then it is probably a bug of the TPM software on your Windows machines. More information on that can be found in the SCEPman documentation.
If you see something like this in your Logs
... there can be two reasons. One is that your WiFi profile is referencing the wrong root certificate for server validation. Please make sure that your profile is setup correctly. If it is and you are still facing this issue, try to set your KSP to Software KSP.
The setting Key Storage Provider (KSP) determines the storage location of the private key for the end-user certificates. Storage in the TPM is more secure than software storage, because the TPM provides an additional layer of security to prevent key theft. However, there is a bug in some older TPM firmware versions that invalidates some signatures created with a TPM-backed private key. In such cases, the certificate cannot be used for EAP authentication as it is common for Wi-Fi and VPN connections. Affected TPM firmware versions include:
STMicroelectronics: 71.12, 73.4.17568.4452, 71.12.17568.4100
Intel: 11.8.50.3399, 2.0.0.2060
Infineon: 7.63.3353.0
IFX: Version 3.19 / Specification 1.2
If you use TPM with this firmware, either update your firmware to a newer version or select "Software KSP" as key storage provider.
If your Logs contain rejections with the error "Cannot continue, as the peer is misbehaving" this indicates that the client stopped communicating with the RADIUS service, mostly because the trust settings are incorrect. In this case, please verify the certificates on the affected devices.
If your (proxy) Logs contain error messages similar to the ones shown below
then one of your access points or switches that is trying to connect to your RADIUSaaS instance via a RADIUS Proxy is using a mismatched Shared Secret.
To identify the affected access point or switch, first determine the RADIUS proxy by expanding the error message and searching for the proxyip property. Now that you know the proxy, use your inventory and knowledge of specific locations or groups of devices that cannot connect to your network to identify the misconfigured network device. Finally, update the shared secret to match the value configured in your RADIUSaaS instance for that proxy.
When you want to use your own server certificate, your RADIUS server requires the complete certificate chain in order to let other participants (Proxy, RadSec clients, endpoints that try to connect) verify the server's identity. If you see this message, either copy & paste the CA certificate below the server certificate in the textfield or create a PCKS8 certificate bundle which includes all certificates from the lead to the root.
In order to log in to the RADIUSaaS web portal ("RADIUSaas Admin Portal"), the following requirements have to be met:
The UPN/email address you provided as technical admin has to be authenticatable against some Microsoft Entra ID (Azure AD) (it does not have to be an identity from the tenant whose users will leverage RADIUSaaS for network authentication).
The UPN/email address you provided as technical admin must have been registered on your RADIUSaaS instance as described here. In case it is the initial admin, please contact us if you believe we registered the wrong user.
The Microsoft Entra ID (Azure AD) user object behind the UPN/email address has to be entitled to grant the RADIUSaaS Enterprise Application the following permissions (see screenshot below):
Read the Basic User Profile
In case your Microsoft Entra ID (Azure AD) user has no rights to grant the required permissions, no corresponding Enterprise Application will be auto-created in your Microsoft Entra ID (Azure AD). To circumvent this, ask your IT department to grant your user the needed permissions.
Wi-Fi configuration does not get deployed if Wi-Fi, SCEP and Trusted certificate profiles are assigned to different groups. They might show up as "Pending" or there is no status at all. Please use the same group or "All devices" resp. "All users" for all linked profiles.
You can assign the SCEP Root certificate profile to both "All users" and "All devices" if you have a device (assigned to "All devices)" and user certificate (assigned to "All users") in use.
Android seems to require an UPN in Subject alternative name in newer versions (even for device certificates). Please add this in your SCEP profile (e.g. {{DeviceId}}@contoso.com):
Common error codes: 0xc7d24fc5 or -942518331
Key points are:
select the Root CA certificate for server validation (important: do not upload the server certificate of the RADIUSaaS) - and -
define a radius server name
Note: There seems to be a character limit for this field. To solve possible issues, you might just use the domain part without subdomain like "radius-as-a-service.com" (instead of "contoso.radius-as-a-service.com").
Android developers states: "[...] must configure both a Root CA certificate, and either a domain suffix match or an alternate subject match". So, the MDM can use "setAltSubjectMatch" or "setDomainSuffixMatch" after adding a root certificate to the Wi-Fi configuration. Intune seems to use "setDomainSuffixMatch" as just "radius-as-a-service.com" is sufficient.
sometimes identity privacy is needed (e.g. seen on Android kiosk devices / Android Enterprise dedicated)
Maintain access to data you have given it access to (allow request of refresh token)
