Server certificates
The Server certificates page manages the certificates Airgate presents as a server: the HTTPS certificate of the console, guest portal and API, and the RADIUS identities that Wi-Fi clients see during EAP and that network devices see over RadSec. Administrators use it to check expiry, generate or upload a certificate, and give the tenant its own EAP identity.
The page sits in the Certificates tab, at the console path /admin/server-certs.
What this page shows
Section titled “What this page shows”Certificates › Server certificates opens a page titled Server Certificates with these sections:
- Console: the Console HTTPS certificate (
platform-https). Browsers see it on the console, the guest portal and the API. It is issued by the console’s root CA (trust that root from Certificate authorities), or you upload one from a public CA. - FreeRADIUS certificate directory: the status of the certificate files Airgate writes for FreeRADIUS.
- This tenant: the Tenant EAP identity (
tenant-eap), what this tenant’s supplicants see during EAP. - Platform (shared by every tenant): the Platform EAP certificate (
platform-eap) and the Platform RadSec certificate (platform-radsec), issued by the platform root CA or uploaded by the platform administrator. The section notes where generated names come from and the default key type.
Each certificate appears as a card. The left side shows its source (Generated, Uploaded or Not configured), a Platform managed badge when you cannot change it, an Expiring or Expired badge within 30 days of expiry, the days left and a lifetime bar. Generated certificates renew automatically 30 days before they expire; uploaded certificates are never renewed, so replace them before they expire.
| Certificate | What it is |
|---|---|
| Console HTTPS certificate | Served by Airgate itself. A new certificate is used from the next connection. |
| Tenant EAP identity | Optional dedicated 802.1X server certificate for this tenant. Supplicants then validate this tenant’s own server name. Without it, the tenant’s supplicants are served the shared platform EAP certificate. |
| Platform EAP certificate | The shared 802.1X (EAP-TLS / PEAP) server identity for every tenant without a dedicated identity. |
| Platform RadSec certificate | The TLS identity of the RadSec listener (TCP 2083) that network devices connect to. Network devices validate it against the platform root. |
Fields and columns
Section titled “Fields and columns”Certificate card
Section titled “Certificate card”| Field | Meaning |
|---|---|
| Server names | The DNS names the certificate covers. |
| Subject | The certificate subject. |
| Issuer | The issuer, with a view CA link when Airgate’s CA issued it. |
| Valid | Start and end dates, with a countdown. |
| Key type | For a generated certificate, also the key type used on regeneration if it differs. |
| Serial, SHA-256 | Identifiers, with copy buttons. |
| Chain | How many certificates follow the leaf, or Leaf only. |
| FreeRADIUS file / Served by | The file FreeRADIUS reads, or nacd HTTPS listener for the console certificate. |
| Certificate record | For a tenant certificate, a link to it in Issued certificates. |
| Last changed | When the certificate was last replaced. |
| Default names, Name source, Default key type | Shown when the certificate is not configured, or when the current names differ from the defaults. |
FreeRADIUS certificate directory
Section titled “FreeRADIUS certificate directory”| Field | Meaning |
|---|---|
| Directory | Managed when Airgate writes the directory, with its path; Not written when RADIUS_CERT_DIR is empty. |
| Last sync | OK, Failed (with the error) or Not yet. The sync runs at start, every 5 minutes and after changes. |
| Reload signal | How FreeRADIUS is told to reload (docker kill -s HUP or SIGHUP (pid file)), and when it was last sent; Disabled when RADIUS_CONTROL is not set. |
| This tenant | How many Onboard and NAD CAs FreeRADIUS trusts for this tenant, and the file of the tenant’s EAP identity (or the shared platform file). |
Generate dialog
Section titled “Generate dialog”| Field | Meaning |
|---|---|
| Server names (DNS SANs) | The names to cover; the first becomes the CN. Editable for the console and tenant certificates. The platform EAP and RadSec names are fixed by the server configuration; upload a certificate to use other names. |
| Validity (days) | 1 to 825. Default 397. |
| Key type | Server default or a key type such as RSA 2048 or ECDSA P-256. |
Platform certificates are issued by the platform root CA. The tenant EAP identity is issued by the tenant’s active Onboard CA and listed under Issued certificates with type Server. The private key is generated and kept sealed on the server; it is never shown. The dialog warns when:
- it replaces an uploaded certificate;
- the tenant’s current generated certificate will be revoked with reason superseded;
- the server names change: devices onboarded earlier pinned the old names and refuse the new certificate until they re-onboard, unless those names are listed as trusted server names in the provisioning settings;
- the certificate is a platform EAP or RadSec certificate: FreeRADIUS must be restarted to serve it, and the change affects every tenant.
Upload dialog
Section titled “Upload dialog”| Field | Meaning |
|---|---|
| Server certificate | Required. PEM, leaf first; its intermediates may follow. Load certificate file reads it from a file. |
| Private key | Required. The matching unencrypted PEM key (PKCS#8, PKCS#1 or SEC1). Stored sealed; never displayed or returned. |
| Chain (optional) | Intermediates and optionally the root, in order. |
Requirements: a certificate from a CA your clients already trust, a matching unencrypted key, RSA 2048 or larger or ECDSA P-256 or larger, not a CA certificate, valid for more than 24 hours, the serverAuth EKU when an EKU is present, and a chain in order. Server names come from the DNS SANs, or the CN. Uploaded certificates are never renewed automatically.
Actions
Section titled “Actions”| Action | Where | What it does |
|---|---|---|
| Refresh | Page header | Reloads the certificates and the directory status. |
| PEM, DER, Chain | Card | Downloads the certificate as PEM, DER (.cer), or followed by its chain. |
| View PEM / Hide PEM | Card | Shows the certificate and chain in PEM. |
| Upload custom | Card | Opens the upload dialog. Upload & activate replaces the certificate. |
| Generate / Regenerate | Card | Opens the generate dialog and issues a new certificate. |
| Dedicated EAP identity toggle | Tenant EAP identity card | Turning it on opens the generate dialog; turning it off asks to remove the identity. |
| Remove | Tenant EAP identity card | Asks for confirmation, then removes the tenant’s EAP identity. The tenant goes back to the shared platform EAP certificate, and a generated certificate is revoked (cessation of operation). Devices that pinned the tenant’s server name fail server validation until they re-onboard, unless the platform certificate also serves that name. |
Permissions
Section titled “Permissions”- View:
admin:read: Tenant Administrator, Network Administrator, Read-only Administrator and Platform Administrator. - Change:
onboard:write, which Tenant Administrator, Network Administrator and Platform Administrator hold. The platform certificates (console HTTPS, platform EAP and platform RadSec) can be changed only by a Platform Administrator; for other roles they show Only a platform administrator can change it.