Certificate authorities
The Certificate authorities page shows the trust chain of Airgate’s built-in PKI: the platform root CA and the tenant’s own intermediate CAs. Administrators use it to download the root CA that devices and network devices must trust, inspect each CA, rotate a CA, and turn on SCEP enrolment for an MDM such as Microsoft Intune.
What this page shows
Section titled “What this page shows”Certificates › Certificate authorities shows the CAs as a tree:
- Platform Root CA: the root at the top. It signs every tenant’s Onboard and NAD CAs and the shared platform EAP and RadSec server certificates. The platform operator manages it; it carries a Platform managed badge.
- Onboard CA: the tenant’s CA for EAP-TLS client certificates, SCEP certificates and tenant server certificates.
- NAD CA (RadSec): the tenant’s CA for the RadSec certificates of network devices.
CAs that a previous platform root issued appear under Issued by a previous platform root. Retired CAs are not shown.
Each CA node shows its name, type, status, subject, key type, a lifetime bar and when it expires. Tenant CAs also show the number of certificates they Issued, how many are Valid and how many are Revoked; the root shows how many Tenant CAs it signed.
A CA has one of three statuses:
| Status | Meaning |
|---|---|
| Active | Issues new certificates. |
| Retiring | Replaced by a rotation. It stays trusted and keeps answering OCSP and CRL requests until none of its certificates is still valid. |
| Retired | None of its certificates is valid any more. The hourly sweep sets this status. |
Select a CA to open the Certificate authority panel.
Fields and columns
Section titled “Fields and columns”Certificate authority panel
Section titled “Certificate authority panel”| Field | Meaning |
|---|---|
| Validity | A lifetime bar from the start date to the expiry. |
| Common name | The CA’s common name. |
| Issuer | Self-signed for the root, otherwise the CA that signed it. |
| Serial, Subject key ID | Identifiers, with copy buttons. |
| Key type | For example RSA 2048, RSA 3072, RSA 4096, ECDSA P-256 or ECDSA P-384. |
| Valid from, Valid until | Validity dates, with a countdown to expiry. |
| Created | When the CA was created. |
| SHA-256, SHA-1 | Fingerprints, with copy buttons. |
| Issues (root) | The tenant CAs the root signed, with their status and expiry. |
| Issued certificates (tenant CAs) | Issued, valid and revoked counts. |
| OCSP responder | The OCSP URL for certificates of this CA. |
| CRL | The CRL download URL. |
| CA issuers (AIA) | The URL of the CA certificate. |
| CRL number, CRL next update | The current CRL number and when it is next generated. A CRL is generated on its first download or by the hourly sweep. |
| Certificate | The CA certificate in PEM. |
SCEP section (active Onboard CA)
Section titled “SCEP section (active Onboard CA)”The panel of the active Onboard CA has a SCEP section. SCEP always issues from the tenant’s active Onboard CA.
| Field | Meaning |
|---|---|
| Issue certificates from this CA over SCEP | Turns SCEP enrolment on. |
| SCEP URL | The URL to put in the MDM’s SCEP profile: https://<airgate-host>/scep/<tenant-slug>. Devices must reach it from the internet. |
| Certificate lifetime (days) | 1 to 3650. |
| Static challenge | A fixed SCEP password for MDMs that need one (for example Jamf or Workspace ONE). At least 8 characters. Not needed for Intune. |
| Check SCEP requests with Microsoft Intune | Intune sends a one-time challenge with each request, and Airgate validates it with Intune before it issues a certificate. The app registration needs the Intune scep_challenge_provider permission. |
| Directory (tenant) ID | The Microsoft Entra tenant ID of the app registration. |
| Application (client) ID | The app registration’s client ID. |
| Client secret | The app registration’s client secret. |
Generate one-time SCEP challenge
Section titled “Generate one-time SCEP challenge”A one-time challenge binds an enrolment to a user: the certificate’s CN, UPN and email SAN, and the device MAC URN come from the challenge, not from the device’s request.
| Field | Meaning |
|---|---|
| Owner | Required. The user the certificate is issued to, for example alice@contoso.com. |
| Device name | Optional. |
| Device MAC | Optional, for example 02:11:22:33:44:55. |
| Valid for | 15 minutes, 1 hour (default), 4 hours, 24 hours or 7 days. |
The challenge value is shown once, with the SCEP URL, the owner and the expiry. Only a hash is stored. The first successful enrolment consumes it.
One-time challenges list
Section titled “One-time challenges list”| Column | Meaning |
|---|---|
| Owner | The user the challenge is for. |
| Device | Device name and MAC, if given. |
| Status | Outstanding, Used or Expired. Filter with Outstanding, Used, Expired or All. |
| Expires / used | Time to expiry, or when it was used. |
| Created | When the challenge was created. |
Replace the platform root CA
Section titled “Replace the platform root CA”Platform administrators only. The dialog shows the current root (Subject, Source, Key type, Valid until, SHA-256) and download buttons Root CA (PEM), Root CA (.cer) and, for an imported intermediate, Full chain.
| Field | Meaning |
|---|---|
| Create a new root | Common name (required), Organization, Organizational unit, Country (two letters), Key type and Valid for (years) (1 to 30). The key is created on the appliance and stored encrypted. |
| Import your own CA | PKCS#12 (.p12 / .pfx) with its Password, or PEM certificate + key (CA certificate, Private key, and Issuer chain for an intermediate). The CA must be allowed to sign CAs and be valid for at least another year. |
| Type REPLACE to confirm | Type REPLACE to enable the button. |
Actions
Section titled “Actions”| Action | Where | What it does |
|---|---|---|
| Root CA | Page header | Downloads the platform root certificate (PEM): the trust anchor that supplicants and network devices install. |
| Replace root CA | Page header (platform administrators) | Opens Replace the platform root CA. Airgate moves the tenant CAs under the new root and re-issues the Wi-Fi (EAP), RadSec and console certificates, so the Wi-Fi server certificate changes. Uploaded server certificates are kept. Every device that trusts the current root must be given the new one. |
| Refresh | Page header | Reloads the CAs. |
| View issued certificates | Panel | Opens Issued certificates filtered by this CA. |
| Rotate CA | Panel (active tenant CAs) | Creates a new CA of the same type under the platform root and makes it active; the current CA becomes Retiring. Its valid certificates keep working. Confirm with I understand that the rotation cannot be undone. |
| PEM, DER, Chain | Panel, Certificate | Downloads the CA certificate as PEM, as DER (.cer), or followed by its issuing chain. The root has no Chain button. |
| Save SCEP settings / Cancel | SCEP section | Saves or discards SCEP and Intune settings. |
| Test Intune connection | SCEP section | Checks the saved Intune app registration and shows the validation service URL, or the error. Save first. |
| One-time challenge | SCEP section | Opens Generate one-time SCEP challenge. |
| Delete | One-time challenges list | Withdraws an outstanding challenge (an MDM profile that still carries it fails to enrol), or deletes the record of a used or expired one. Certificates already issued are not affected. |
Permissions
Section titled “Permissions”- View:
onboard:read: Tenant Administrator, Network Administrator, Help Desk, Read-only Administrator and Platform Administrator. - Change:
onboard:write: Tenant Administrator, Network Administrator and Platform Administrator. Rotating a CA, saving SCEP and Intune settings, testing Intune and managing one-time challenges needonboard:write. - Replace root CA:
platform:admin: Platform Administrator only.