Skip to content

Certificates and trust

Airgate runs its own public key infrastructure (PKI). This guide explains which certificates exist, how to give the console your own name, how to get the root CA onto devices, how to replace the root with your own CA, and how to control which outside CAs Airgate trusts.

Platform Root CA (self-signed, or your own CA)
├── Onboard CA (one per tenant) issues device certificates: Intune SCEP, BYOD, admin-issued
├── NAD CA (RadSec, one per tenant) issues switch and AP certificates for RadSec
├── Platform EAP certificate the RADIUS server certificate devices check (PEAP, EAP-TLS, TTLS)
├── Platform RadSec certificate the RadSec listener (TCP 2083)
└── Console HTTPS certificate when generated by Airgate

Devices need to trust only the Platform Root CA. It covers the RADIUS server certificate (so PEAP, TTLS and EAP-TLS clients accept the server) and, for EAP-TLS, the device certificates themselves.

  • Platform administrator for the console certificate, the platform EAP certificate and Replace root CA. Tenant administrators can view the CAs and manage Trusted CAs.
  • The DNS name administrators and devices will use for the console, for example nac.contoso.com.

The console, the guest and BYOD portals, SCEP and the API are served over HTTPS by Airgate on one port (8443 by default, published as you configured the installation).

  1. Open Certificates › Server certificates and find Console HTTPS certificate.
  2. Choose one:
    • Generate: enter the name people use under Server names (DNS SANs), for example nac.contoso.com, the Validity (days) (1 to 825, default 397) and the Key type. It is issued by the Airgate root and renewed automatically 30 days before it expires.
    • Upload custom: a certificate from a public CA. Paste or load the Server certificate (leaf first), the Private key and the Chain (optional), then select Upload & activate. Browsers trust it without further steps. Renew it yourself before it expires.
  3. The new certificate is used from the next connection; nothing restarts.
  4. Point DNS for the name at Airgate and set PUBLIC_URL to https://nac.contoso.com. Airgate builds links, the SCEP URL and the SSO addresses from it.
  1. Open Certificates › Certificate authorities.
  2. Select Root CA at the top of the page to download the root as PEM (.pem), or select the Platform Root CA row and, in the drawer under Certificate, select DER to get a .cer file (the format Intune expects) or PEM.

The root can also be downloaded without signing in from the CA issuers (AIA) address shown in each CA’s drawer under Revocation & distribution.

  • Intune-managed devices: a Trusted certificate profile (see Intune SCEP overview).
  • Windows, by hand (administrator PowerShell): Import-Certificate -FilePath .\airgate-root.cer -CertStoreLocation Cert:\LocalMachine\Root
  • macOS, by hand: open the file in Keychain Access, add it to the System keychain, open it and set When using this certificate to Always Trust.
  • Group Policy: Computer Configuration › Policies › Windows Settings › Security Settings › Public Key Policies › Trusted Root Certification Authorities › Import.
  • BYOD devices get the root inside their profile or app (see BYOD onboarding).

Step 4: Check the RADIUS server certificate name

Section titled “Step 4: Check the RADIUS server certificate name”

Devices that check the server (the right setting) compare the RADIUS certificate’s name with the name in their Wi-Fi profile.

  1. Open Certificates › Server certificates.
  2. Look at Platform EAP certificate › Server names, for example radius.contoso.com. If your tenant has a Tenant EAP identity turned on (Dedicated EAP identity), its Server names are used instead.
  3. Enter exactly this name in every Wi-Fi profile (Certificate server names in Intune, Domain on Android, TLSTrustedServerNames in Apple profiles).

Choose the name before you roll out profiles. Changing it later means updating every profile.

Step 5 (optional): Replace the root with your own CA

Section titled “Step 5 (optional): Replace the root with your own CA”

A platform administrator can replace the Airgate root, for example to use a root with your company name or an intermediate of your corporate PKI.

  1. Open Certificates › Certificate authorities and select Replace root CA.
  2. Under New root, choose:
    • Create a new root: Common name (the name devices show), Organization, Organizational unit, Country (two letters), Key type and Valid for (years) (1 to 30). The key is created on the server.
    • Import your own CA: PKCS#12 (.p12 / .pfx) with its Password, or PEM certificate + key (CA certificate, Private key as unencrypted PEM, and for an intermediate the Issuer chain up to the root). The CA must be allowed to sign CAs below it (no path length 0), use RSA 2048 bits or more or ECDSA, and be valid for at least another year.
  3. Type REPLACE and select Replace root CA.

What happens:

  • The new root becomes active. The old one is kept as Retiring: its OCSP and CRL keep answering.
  • Every tenant’s Onboard CA and NAD CA is rotated under the new root. The old ones stay trusted until the certificates they issued expire.
  • Generated server certificates (EAP, RadSec, console) are issued again under the new root. Uploaded certificates are not changed.
  • The result dialog, Root CA replaced, lets you download the new root for your MDM.

The CA keys are stored in the database, encrypted with MASTER_KEY. Back up both: a rebuilt server needs them to keep the same root.

Step 6: Decide which outside CAs Airgate trusts

Section titled “Step 6: Decide which outside CAs Airgate trusts”

Open Certificates › Trusted CAs.

Purpose (Trust it for) Used when Public CAs allowed
Wi-Fi client certificates Devices sign in with EAP-TLS. Never: anyone can buy a public certificate.
Network devices (RadSec) Switches and APs connect over RadSec. Never.
Directories LDAPS, Active Directory and HTTP directory servers. Yes (default on).
Outbound connections Webhooks, log export and integrations. Yes (default on).
  • Public CAs: the well-known roots browsers trust, kept up to date with the server. Untick a purpose to stop trusting them for it.
  • Import CA: paste or load a CA certificate (PEM or DER; a bundle imports each CA), choose Trust it for, select Import. Typical cases:
    • the AD CS root for LDAPS (Directories);
    • a company PKI whose certificates should get on Wi-Fi (Wi-Fi client certificates);
    • the CA of an internal syslog or SIEM server (Outbound connections).
  • Airgate’s own CAs (Certificate authorities) are always trusted for Wi-Fi and RadSec; do not import them.
  • Turning a CA off (On) or removing it takes effect within a minute.
  • Open https://nac.contoso.com in a browser on a device that trusts the root: no certificate warning.
  • On a Windows PC, run certutil -store root and find the Airgate root.
  • Connect with PEAP or EAP-TLS; Monitor › Sign-in log shows the sign-in.
Symptom Cause Fix
Sign-in log: The device didn’t trust Airgate’s RADIUS certificate The device does not have the Airgate root, or its profile expects another server name. Push the root (step 3); match Certificate server names to step 4.
Sign-in log: The device’s certificate isn’t from a CA Airgate trusts The device used a certificate from a CA not trusted for Wi-Fi client certificates. Use an Airgate certificate, or import the CA with that purpose.
Sign-in log: The device stopped answering during sign-in The user cancelled a certificate prompt, or the device does not trust the server. Check the profile’s root and server name.
Browser warns about the console certificate The console certificate is generated and the root is not trusted, or the name does not match. Install the root, or upload a public certificate for the name.
Directory test fails with a certificate error The directory’s CA is not trusted for Directories. Import it with that purpose.
© 2026 Airowire Networks Pvt. Ltd. Airgate is a product of Airowire.Product · Release notes · Security