Certificates and PKI
Airgate has its own public key infrastructure (PKI). It issues the client certificates devices use for EAP-TLS, the certificates network devices use for RadSec, and the server certificates Airgate presents. This page explains the certificate authorities, how certificates are issued and revoked, which CAs Airgate trusts, and which server certificates exist.
The trust chain
Section titled “The trust chain” Platform root CA (one per Airgate platform; devices install it as trust anchor) │ ├── Tenant Onboard CA issues Wi-Fi client certificates (EAP-TLS): │ SCEP, BYOD portal, admin-issued ├── Tenant NAD CA issues RadSec client certificates for switches, APs │ and site connectors │ ├── RADIUS (EAP) server certificate presented to Wi-Fi clients ├── RadSec server certificate presented to network devices └── Console HTTPS certificate (generated)| Certificate authority | Purpose |
|---|---|
| Platform root CA | The trust anchor. Created when Airgate first starts. Everything below chains up to it. Devices and network devices install it so that they trust Airgate’s server certificates. A platform administrator can replace it (Certificates › Certificate authorities › Replace root CA) with a new root or with your own CA. |
| Onboard CA (per tenant) | Issues EAP-TLS client certificates for the tenant’s users and devices. |
| NAD CA (per tenant) | Issues RadSec client certificates for the tenant’s network devices and site connectors. |
The CA private keys are stored in the database, sealed with the platform’s master key. Download the root certificate from Certificates › Certificate authorities (for example Root CA (.cer) for an Intune trusted certificate profile).
How certificates are issued
Section titled “How certificates are issued”| Way | Who uses it |
|---|---|
| SCEP | MDMs such as Microsoft Intune, Jamf Pro or Workspace ONE enrol managed devices at https://<console address>/scep/<tenant>. |
| BYOD portal | Users onboard their own devices and get one certificate per device. See BYOD. |
| Issue certificate | An administrator issues a certificate on Certificates › Issued certificates. |
| RadSec | Certificates for network devices and site connectors, from the NAD CA. A site connector gets its certificate when it enrols. |
Certificates › Issued certificates lists every certificate the tenant’s CAs issued, with its owner, device MAC address, issuing CA, how it was issued (Issued via) and status. You can filter, export to CSV and revoke.
SCEP is turned on per tenant on Certificates › Certificate authorities with Issue certificates from this CA over SCEP. The settings are:
| Setting | Meaning |
|---|---|
| SCEP URL | The address to put in the MDM’s SCEP profile. Devices must reach it from the internet. |
| Certificate lifetime (days) | 1 to 3650. |
| Static challenge | A fixed SCEP password for MDMs that use one (Jamf Pro, Workspace ONE). Not needed for Intune. |
| One-time challenge | A single-use challenge for one owner and device, shown only once. |
| Check SCEP requests with Microsoft Intune | Validate each request with Intune before issuing. |
Intune SCEP validation
Section titled “Intune SCEP validation”Intune puts its own signed, encrypted challenge into each device’s SCEP request. With Check SCEP requests with Microsoft Intune on:
- A request whose challenge is not one of Airgate’s own is sent to Intune for validation.
- Airgate issues the certificate only when Intune answers that the request is valid.
- Airgate then tells Intune that the certificate was issued (or that issuing failed), so the Intune admin center shows the device’s certificate state.
This needs an app registration in your Microsoft Entra tenant with the application permissions Microsoft Intune API › scep_challenge_provider and Microsoft Graph › Application.Read.All, and its Directory (tenant) ID, Application (client) ID and Client secret. Test Intune connection checks them. See Deploy Wi-Fi certificates to Windows with Intune SCEP.
Revocation: OCSP and CRL
Section titled “Revocation: OCSP and CRL”Every certificate the tenant’s CAs issue carries:
- an OCSP address:
<PKI address>/ocsp/<CA id>; - a CRL address:
<PKI address>/crl/<CA id>.crl, and the issuer certificate at<PKI address>/crl/<CA id>.crt.
The PKI address is the console address unless the operator sets a separate one (typically plain HTTP, as OCSP and CRL clients expect).
Airgate checks the status of its own certificates directly at every EAP-TLS sign-in, and its RADIUS server also asks the OCSP responder. A revoked certificate is refused at the next sign-in with The device’s certificate was revoked.
When you revoke a client certificate, Airgate also disconnects the sessions that used it (by the certificate’s device MAC address, or, without one, the owner’s active sessions when the owner has no other valid certificate). See Change of Authorization.
Trusted CAs
Section titled “Trusted CAs”Certificates › Trusted CAs decides which certificate authorities the tenant trusts, and for what:
| Purpose | Trusted when Airgate… | Public CAs |
|---|---|---|
| Wi-Fi client certificates | accepts EAP-TLS client certificates | Never |
| Network devices (RadSec) | accepts RadSec client certificates from switches and APs | Never |
| Directories | connects to LDAPS, Active Directory and HTTP directory servers | Allowed |
| Outbound connections | connects to webhooks, log export and integrations | Allowed |
- The tenant’s own CAs (Certificate authorities) are always trusted for Wi-Fi and RadSec. They need no import.
- Public CAs are the well-known roots that browsers trust. Untick a purpose to stop trusting them for it.
- Import CA adds a CA certificate (PEM or DER; a bundle imports each CA) with the purposes you tick. Typical imports: your AD CS root for LDAPS, a company PKI whose certificates should get on Wi-Fi, an internal SIEM’s CA.
- A client certificate from an imported CA is bound to the tenant that imported it.
Server certificates
Section titled “Server certificates”Certificates › Server certificates shows the certificates Airgate presents:
| Certificate | Presented to | Notes |
|---|---|---|
| Console (HTTPS) | Browsers, MDMs (SCEP), site connectors, API clients | Generated by the root CA, or uploaded from a public CA. |
| RADIUS (EAP) server identity | Wi-Fi and wired clients during PEAP, EAP-TTLS and EAP-TLS | Shared by every tenant on the platform, or a tenant-specific identity. Devices check its name and its CA. A generated tenant identity is renewed automatically 30 days before it expires. |
| RadSec server identity | Network devices and site connectors connecting over RadSec | Platform-wide. |