Digital certificates form the cryptographic backbone of Cisco wireless infrastructure, securing the Control and Provisioning of Wireless Access Points (CAPWAP) discovery and Datagram Transport Layer Security (DTLS) tunnel establishment between access points (APs) and Wireless LAN Controllers (WLCs). When an AP certificate lapses or fails validation, entire fleets of access points can become stranded—failing DTLS handshakes, dropping client traffic, or falling into endless reboot loops.
Proactively inspecting certificate validity, understanding certificate lifecycles, and knowing how to troubleshoot expired credentials across both legacy Cisco AireOS and modern Catalyst 9800 systems is an essential operational discipline for enterprise network engineers. This guide walks through Cisco AP certificate architecture, official advisories, inspection commands across all platforms, comparative trustpoint behaviors, emergency recovery steps, and production deployment templates for Locally Significant Certificates (LSC).
Table of Contents
Cisco AP Certificate Types and Lifecycle: MIC, SSC, and LSC
To effectively manage and troubleshoot Cisco wireless certificates, administrators must distinguish between the three primary certificate types deployed across APs and controllers.
What is a Manufacturer Installed Certificate (MIC)?
A Manufacturer Installed Certificate (MIC) is an X.509 digital certificate embedded into the AP’s physical hardware during assembly. Stored inside a cryptographic chip known as the Secure Unique Device Identifier (SUDI), the MIC is signed by the Cisco Manufacturing Certificate Authority (CA) (e.g., Cisco Manufacturing CA or Cisco Manufacturing CA SHA2). It authenticates the access point as genuine Cisco hardware during the initial DTLS handshake with a WLC. Physical controllers (such as the Catalyst 9800-40, 9800-80, 9800-L, and AireOS 3504, 5520, and 8540) also carry factory-installed MICs to authenticate themselves to joining APs.
What is a Self-Signed Certificate (SSC)?
A Self-Signed Certificate (SSC) is an identity certificate generated locally by the controller’s operating software rather than an external or manufacturing CA. SSCs are standard on virtualized wireless platforms—such as the Cisco Catalyst 9800-CL and legacy AireOS Virtual WLC (vWLC)—which lack physical cryptographic chips. When APs join a virtual controller using an SSC, they cannot validate the controller against a pre-installed root trust anchor; instead, the AP accepts the controller’s public key fingerprint (often authenticated through an AP join authorization list or explicit hash check).
What is a Locally Significant Certificate (LSC)?
A Locally Significant Certificate (LSC) is a custom digital certificate issued to the AP and controller by an enterprise’s private Public Key Infrastructure (PKI) Certificate Authority (such as Microsoft Active Directory Certificate Services, EJBCA, or an internal OpenSSL CA). LSCs replace or supersede factory-installed MICs for CAPWAP DTLS authentication. Using LSCs provides enterprise security teams full operational control over cryptographic key lengths (2048-bit or 4096-bit RSA, or ECDSA), expiration intervals, certificate revocation policies (CRL/OCSP), and scheduled renewal workflows.
How long do Cisco AP certificates remain valid?
Historically, Cisco factory MICs using SHA-1 hashing were configured with an unalterable validity lifespan of exactly 10 years from the date of manufacture. As these units pass a decade in service, their certificates expire automatically. Modern Cisco APs and controllers manufactured with SHA-256 certificates feature extended validity periods (typically up to 2099 or matching the hardware support envelope). SSC certificates on virtual controllers typically default to 10 or 15 years upon initial creation, while LSC lifecycles are governed entirely by the issuing organization’s PKI policy (commonly 1 to 3 years).
What occurs when an AP MIC expires, and can it be renewed?
Because the MIC is permanently burned into the hardware crypto chip at the factory, a MIC cannot be re-issued, updated, or renewed. When a MIC reaches its expiration date, the WLC rejects the AP’s CAPWAP join request due to an X.509 certificate validation failure. To restore or maintain connectivity after MIC expiration, administrators must either configure the controller to ignore the certificate expiration date or migrate the access point fleet to Locally Significant Certificates (LSC).
Official Cisco Field Notices on AP Certificate Expiration
Cisco has documented certificate expiration behaviors and their operational impacts across several critical Field Notices and advisory bulletins:
Field Notice: FN63942 — APs and WLCs Fail to Create CAPWAP Connections Due to Certificate Expiration
- Primary Condition: Cisco Lightweight APs manufactured between July 18, 2005, and mid-2017 carry a 10-year SHA-1 MIC lifespan.
- Impact: Once an access point or physical WLC crosses the 10-year timestamp from its build date, CAPWAP DTLS handshakes fail with certificate verification errors. Unaffected APs currently joined remain operational until they reboot, lose power, or switch controllers, at which point re-joining fails.
- Affected Hardware: Legacy Cisco Aironet 1130, 1140, 1240, 1250, 1260, 2600, 3500, 3600, and early revisions of 1700, 2700, and 3700 series APs.
Field Notice: FN72524 — Cisco IOS APs Stuck in Downloading State After December 4, 2022
- Primary Condition: Light-weight Cisco IOS software images built between December 2012 and November 2022 relied on an internal Cisco code-signing digital certificate that expired on December 4, 2022, at 23:59:59 UTC.
- Impact: When an access point downloads software during a version upgrade, downgrade, or controller change, the AP verifies the cryptographic signature of the downloaded
.tarimage. Because the signing certificate expired, image validation fails, causing the AP to enter an infinite image-download and reboot loop. - Affected Hardware: All lightweight APs running Cisco IOS: 700, 801, 802, 1530, 1552, 1570, 1600, 1700, 2600, 2700, 3500, 3600, and 3700 series. (Wave 2 and Wi-Fi 6 APs running AP-COS are not subject to this specific code-signing defect).
- Vendor Remediation: Upgrade controllers to releases containing fixed AP software images bundled with updated validation anchors (e.g., AireOS 8.10.196.0+, 8.5.182.12+, or IOS-XE 17.3.7+ / 17.9.3+), or apply an operational clock-rollback during the upgrade window.
Field Notice: FN72424 — Later Hardware Revisions of Wi-Fi 6 APs Fail to Join Controllers
- Primary Condition: Hardware component updates in newer production batches of Catalyst 9105, 9115, 9120, and 9130 series APs introduced new root and intermediate certificate trust anchors in the manufacturing SUDI.
- Impact: Older controller software builds lacking the new intermediate certificates reject CAPWAP connections from these newer AP batches due to unverified trustchains.
- Vendor Remediation: Upgrade controller software to releases containing the updated intermediate CA bundles.
Step-by-Step Guide: How to Check AP Certificate Expiration via CLI
Understanding whether an AP is approaching certificate expiration requires inspecting the device certificate validity interval directly on the AP console or from the managing controller.
+-------------------------------------------------------------+
| Inspection Methods |
+------------------------------+------------------------------+
| AP Local Console | WLC Controller CLI |
| - Cisco IOS: show crypto pki | - AireOS: show certificate |
| - AP-COS: show crypto | - C9800: show wireless mgmt |
+------------------------------+------------------------------+
Step 1: Check Certificate Validity via the AP Console
Connect directly to the access point’s physical console port (RJ45 or USB micro-B) and log into Privileged EXEC mode. The exact command depends on whether the AP runs classic Cisco IOS or modern AP-COS:
On Cisco IOS APs (802.11n and 802.11ac Wave 1 APs):
Execute show crypto pki certificates (or show crypto ca certificates):
AP-3702# enable
Password: *****
AP-3702# show crypto pki certificates Cisco_IOS_MIC_cert
Examine the output under the primary device certificate (ignore the intermediate root CA blocks):
Certificate
Status: Available
Certificate Serial Number (hex): 41A703BC000000214C45
Certificate Usage: General Purpose
Issuer:
cn=Cisco Manufacturing CA
o=Cisco Systems
Subject:
Name: AIR-CAP3702I-A-K9
Serial Number: FCZ1842xxxx
cn=AIR-CAP3702I-A-K9-FCZ1842xxxx
Validity Date:
start date: 14:22:10 UTC Nov 12 2014
end date: 14:32:10 UTC Nov 12 2024
Associated Trustpoints: Cisco_IOS_MIC_cert
Takeaway: The end date confirms precisely when the AP’s MIC expires. If the current controller clock is past this timestamp, DTLS negotiation will fail.
On Cisco AP-COS APs (Wave 2 and Catalyst 9100 Series APs):
On newer access points running AP-COS (Click-OS), run show crypto or check the trustpoint certificate:
AP-9120# enable
AP-9120# show crypto
Locate the Device Certificate section to verify the validity range (Not After or Validity Date end date).
Step 2: Check Certificate Expiration on Cisco AireOS Controllers
From the AireOS CLI, execute the following commands to check controller-side and installed AP certificates:
Verify controller certificates:
cisco
(Cisco Controller) > show certificate summary
This displays a summary table listing Web Administration, Web Authentication, SSC, and MIC validity statuses.Inspect detailed expiration timestamps:
cisco
(Cisco Controller) > show certificate all
Scroll to theDevice Certificate Detailssection:
text
Certificate Type...............: Manufacturer Installed Certificate (MIC)
Certificate Expiration Date....: Fri May 15 18:24:19 2026
Signature Algorithm............: SHA256withRSACheck whether certificate expiration bypass flags are active:
cisco
(Cisco Controller) > show ap cert-expiry-ignore
text
MIC Certificate Expiry Ignore Check ............. Enabled
SSC Certificate Expiry Ignore Check ............. Enabled
Step 3: Check Certificate Expiration on Cisco Catalyst 9800 Controllers
The Catalyst 9800 platform integrates with Cisco IOS-XE’s PKI infrastructure. Run these commands to verify management trustpoints and certificate lifespans:
Check the active wireless management trustpoint:
cisco
C9800# show wireless management trustpoint
text
Trustpoint Name : CISCO_IDEVID_SUDI
Certificate Info : Available
Certificate Type : MIC
Private key Info : Available
FIPS suitability : Not Applicable
(Note: On virtual 9800-CL controllers, the Certificate Type will readvWLC-SSCor custom LSC).Inspect trustpoint validity dates:
cisco
C9800# show crypto pki certificates CISCO_IDEVID_SUDI
text
Certificate
Status: Available
Certificate Serial Number (hex): 72A3C124
Certificate Usage: General Purpose
Issuer:
cn=Cisco Manufacturing CA SHA2
o=Cisco Systems
Subject:
cn=C9800-40-K9-FOC2315xxxx
Validity Date:
start date: 18:30:00 UTC Aug 14 2019
end date: 18:30:00 UTC Aug 14 2029Verify AP join failure events caused by expired certificates:
cisco
C9800# show wireless stats ap join summary | include DTLS|Failed|Invalid
If an AP attempts to connect with an expired MIC, theLast Disconnect Reasoncolumn displaysDTLS handshake failureorCertificate invalid/expired.
Platform Comparison: Certificate Management in Catalyst 9800 vs. AireOS
Managing PKI, trustpoints, and certificate bypass options differs significantly between AireOS and Catalyst 9800 IOS-XE:
| Feature / Criteria | Cisco AireOS (Legacy) | Cisco Catalyst 9800 (IOS-XE) |
|---|---|---|
| Underlying PKI Engine | Proprietary embedded SSL/TLS database | Modular Cisco IOS-XE crypto pki infrastructure |
| Trustpoint Architecture | Flat hierarchy; implicit global binding to AP-Manager | Explicit crypto pki trustpoint linked to wireless management trustpoint |
| Default Virtual WLC Cert | Automatic internal SSC (vWLC-SSC) | SSC generated during Day-0 onboarding or manually generated RSA trustpoint |
| Certificate View Command | show certificate summaryshow certificate all | show wireless management trustpointshow crypto pki certificates [name] |
| AP Certificate Inspection | Log analysis via show msglog or AP console | show wireless stats ap join summaryshow ap auth-list ap-cert-policy |
| Bypass Expired Certs CLI | config ap cert-expiry-ignore mic enableconfig ap cert-expiry-ignore ssc enable | Resolved via software releases extending trust pools; parity CLI available in modern releases (CSCwd80808) |
| LSC SCEP Protocol Support | Native Simple Certificate Enrollment Protocol (SCEP) | Enterprise SCEP via enrollment url and IOS-XE CA trustpoints |
| LSC Fallback Behavior | AP reverts to MIC if LSC authentication fails | AP enters LSC fallback state (joins with MIC, but controller holds AP in non-service state without pushing SSIDs) |
Troubleshooting Cisco AP Join Failures Caused by Expired Certificates
When an access point fails to establish a secure CAPWAP connection, the DTLS session terminates during the certificate validation phase. Follow this logical sequence to isolate, bypass, and resolve the failure.
AP Join Failure Observed
│
▼
Check Console Logs: "%PKI-3-CERTIFICATE_INVALID_EXPIRED"
│
▼
Are APs Bootstrapping / Downloading Code?
├── YES (FN72524 / Loop): ──► Temporarily Roll Back System Clock (NTP disabled)
│ │
│ ▼
│ AP Downloads Code & Rejoins
│ │
│ ▼
│ Restore Clock & Re-enable NTP
│
└── NO (Standard Join / MIC Expired):
│
▼
Apply Immediate Controller Workaround:
(AireOS: config ap cert-expiry-ignore mic enable)
│
▼
Plan Permanent Resolution: Upgrade Software or Deploy LSC
Stage 1: Identify Failure Symptoms and Diagnostic Signatures
When an AP cannot establish DTLS due to an expired certificate, specific error codes are generated:
On the AP Console:
text
[*11/12/2026 14:35:12.0120] DTLS_CLIENT_EVENT: dtls_client_process_record: Error processing Certificate
[*11/12/2026 14:35:12.0125] Cert Verification FAILED with error 10 (certificate has expired) at 0 depth
[*11/12/2026 14:35:12.0130] %PKI-3-CERTIFICATE_INVALID_EXPIRED: Certificate chain validation has failed.On the AireOS WLC (
show msglog):
text
*spamApTask0: Nov 12 14:35:12.110: %SSHPM-3-GENERIC_CERT_ERROR: sshpmPkiApi.c:2240 Certificate validation failed! Reason: Cisco user certificate not verified by cisco root., Certificate type: MICOn the Catalyst 9800 WLC (Radio Control Traces):
text
wncd: %CERT_MGR_ERRMSG-3-CERT_MGR_GENERAL_ERR: Peer certificate verification failed 001A
wncd: %APMGR_TRACE_MESSAGE-3-WLC_GEN_ERR: AP failed to establish CAPWAP DTLS session due to expired certificate
Stage 2: Apply the Immediate Expiration Bypass Workaround
If access points must be recovered immediately in a production environment:
For Cisco AireOS:
Execute the expiry bypass commands in privileged configuration mode:
(Cisco Controller) > config ap cert-expiry-ignore mic enable
(Cisco Controller) > config ap cert-expiry-ignore ssc enable
(Cisco Controller) > save config
Technical Note: This command does not disable cryptography or remove authentication; rather, the WLC still verifies that the certificate was signed by a legitimate Cisco root CA, but ignores the end date validity timestamp.
For Catalyst 9800:
Ensure the controller is running an IOS-XE release containing the updated root certificate definitions and validation bypass capabilities. For APs stuck attempting to validate legacy images under Field Notice FN72524, verify the AP certificate policy allows MIC join:
C9800# configure terminal
C9800(config)# ap auth-list ap-cert-policy allow-mic-ap
C9800(config)# end
Stage 3: Clock-Rollback Procedure for Code Download Recovery (FN72524)
If legacy Cisco IOS APs are trapped in an image-download loop following a software upgrade or migration:
- Disconnect or disable NTP synchronization on the controller:
- AireOS:
cisco
(Cisco Controller) > config time ntp delete 1 Catalyst 9800:
cisco
C9800(config)# no ntp server <IP-Address>Roll the controller clock back to a date prior to December 4, 2022:
- AireOS (via CLI or GUI Commands > Set Time):
cisco
(Cisco Controller) > config time manual 11/01/22 12:00:00 Catalyst 9800:
cisco
C9800# clock set 12:00:00 01 Nov 2022Allow the access points to complete the download:
The APs will validate the software image against the rolled-back system timestamp, install the image to flash, and reboot.Restore correct network time:
Once all APs have successfully downloaded the image and joined, restore the correct date and re-enable NTP servers.
Stage 4: Permanent Remediation
While expiration bypass commands restore network access, the permanent vendor-supported paths are:
1. Controller Software Upgrade: Upgrade AireOS to 8.10.196.0+ or Catalyst 9800 to 17.9.4+ / 17.12.3+ where permanent trust anchors and validation patches are integrated.
2. Deploy Locally Significant Certificates (LSCs): Completely replaces reliance on the factory hardware MIC.
Configuration Templates: Provisioning Locally Significant Certificates (LSC)
Deploying Locally Significant Certificates (LSC) decouples an access point fleet from Cisco factory hardware certificate expirations. The following configuration templates provision LSCs using an external SCEP server (such as Microsoft NDES/CA).
1. Cisco Catalyst 9800 LSC Configuration Template
Step A: Configure PKI Trustpoint and SCEP Enrollment on the C9800
! Generate dedicated RSA keypair for LSC operations
crypto key generate rsa exportable general-keys modulus 2048 label LSC_AP_KEYS
! Define the Certificate Authority Trustpoint
crypto pki trustpoint CA-ENTERPRISE-LSC
enrollment url http://<CA_SERVER_IP>:80/certsrv/mscep/mscep.dll
subject-name CN=C9800-LSC-WLC, OU=Enterprise Wireless, O=Company, C=US
rsakeypair LSC_AP_KEYS
revocation-check none
auto-enroll 80
exit
! Authenticate and fetch the CA Root Certificate
crypto pki authenticate CA-ENTERPRISE-LSC
! Enroll the Controller's Identity Certificate
crypto pki enroll CA-ENTERPRISE-LSC
Step B: Define Global AP LSC Provisioning Parameters
configure terminal
! Configure parameters pushed to APs during SCEP enrollment
ap lsc-provision trustpoint CA-ENTERPRISE-LSC
ap lsc-provision key-size 2048
ap lsc-provision join-attempt 4
ap lsc-provision subject-name-format common-name ap-mac
! Optional: Configure automated LSC renewal prior to expiration
ap lsc-provision renew due-time 30
end
Step C: Enable Provisioning for Access Points
! Option 1: Provision a specific AP by MAC Address
configure terminal
ap lsc-provision mac-address <00a1.b2c3.d4e5>
end
! Option 2: Enable LSC Provisioning globally across all connected APs
configure terminal
ap lsc-provision enable
end
Step D: Bind Management Interface to LSC (Once APs Are Provisioned)
configure terminal
wireless management trustpoint CA-ENTERPRISE-LSC
end
Step E: LSC Verification Commands
show ap lsc-provision summary
show wireless management trustpoint
show ap auth-list ap-cert-policy
2. Cisco AireOS LSC Configuration Template
Step A: Configure SCEP CA Parameters on the WLC
! Define the internal CA URL and credentials
config certificate lsc ca-server url http://<CA_SERVER_IP>:80/certsrv/mscep/mscep.dll
config certificate lsc subject-params country US
config certificate lsc subject-params org "Enterprise Network"
config certificate lsc key-size 2048
Step B: Enroll Controller with the CA Server
! Fetch CA Root Certificate and Enroll Device
config certificate lsc enroll-ca
config certificate lsc enroll-device
Step C: Provision Connected APs with LSC
! Configure AP retry limit before fallback to MIC
config certificate lsc ap-join-attempt 4
! Provision an individual AP or all connected APs
config certificate lsc ap-provision enable <AP_NAME_OR_ALL>
Step D: AireOS Verification Command
show certificate lsc summary
Maintaining situational awareness over Cisco access point certificate lifecycles prevents catastrophic network outages driven by automated X.509 expirations. By routinely inspecting trustpoint validity using platform-specific show commands, understanding the scope of relevant Cisco Field Notices, applying tactical bypass commands during emergencies, and migrating mission-critical APs to enterprise-managed Locally Significant Certificates, network administrators can ensure seamless, uninterrupted CAPWAP connectivity across their enterprise wireless environments.











Comments