6.5.37 Aruba AOS-CX
REST access in read-write mode, the root CA, service names, and the configuration save
The Aruba AOS-CX: Switch Certificates template installs the certificate on an AOS-CX switch through its REST API and assigns it to the services you list. Each renewal gets its own certificate name, and older CertKit versions are deleted once no service uses them.
Requirements
- A Windows CertKit agent with PowerShell 5.1 or later that can reach the switch’s management address over HTTPS. No extra PowerShell modules are needed.
- HTTPS REST access enabled on the switch in read-write mode.
- A switch account in the built-in administrators group.
- The issuing CA’s root certificate, either in a trust anchor profile on the switch or in the agent computer’s Windows Trusted Root Certification Authorities store. When the switch doesn’t have it, the template adds it from Windows as a trust anchor profile named
certkit-ca-.... - The services you list must already be enabled on the switch.
The agent doesn’t validate the switch’s own HTTPS certificate when it connects, so it can reach switches that still serve a self-signed certificate. Use a trusted management network.
Settings
| Setting | What to enter |
|---|---|
| Switch address | The switch’s management hostname or IP. Add :port if HTTPS isn’t on 443. Use the switch’s own address, one deployment per switch. |
| Switch username | An account in the administrators group. |
| Switch password | That account’s password. |
| Services to update | Comma-separated service names: https-server (web interface and REST API), captive-portal, dot1x-supplicant, est-client, hsc, radsec-client, or syslog-client. Availability depends on the switch. Use import-only by itself to install the certificate without assigning it. |
What a deployment does
- Signs in to the REST API.
- Finds or adds a trust anchor profile for the issuing root.
- Imports the certificate as
certkit-<id>-<thumbprint>, unless a matching certificate is already on the switch. - Checks the SHA-256 fingerprints of the leaf and every chain certificate on the switch.
- Assigns the certificate to the listed services.
- Deletes older versions of this CertKit certificate that no service uses.
- Saves the running configuration to the startup configuration, when anything changed.
Updating https-server briefly restarts the switch’s web interface and REST API. The template waits until HTTPS serves the new certificate, then signs in again.
The configuration save
The save copies the entire running configuration to the startup configuration, including any unrelated changes someone left unsaved. Don’t leave unsaved changes on the switch during the deployment window. When nothing changed, nothing is saved.
Common problems
- “No matching self-signed CA root was found in the Windows trusted-root stores”: add the issuing root to the agent computer’s trusted root store, or to a trust anchor profile on the switch. Nothing was written.
- “arubaCxServices must contain comma-separated AOS-CX service names”: check the spelling.
import-onlycan’t be combined with service names. - “Certificate import was not verified within 30 seconds” or “Service associations were not verified within 30 seconds”: the write may have worked. Check the switch before running the deployment again.
- “HTTPS did not serve the expected leaf certificate within 30 seconds”: check the
https-serverassignment on the switch before running again. Nothing was saved or cleaned up. - “Could not reconnect to AOS-CX within 60 seconds”: the web interface restart took longer than expected. Check the switch before running again.
For a product overview, see certificate automation for Aruba AOS-CX.