← Integrations

Automated SSL certificate renewal for Aruba AOS-CX switches

Stop manually installing and assigning certificates on every AOS-CX switch. CertKit handles it for you.

Aruba AOS-CX switches store certificates in their own PKI store and assign them to services with crypto pki application: the web interface, captive portal, RadSec, and syslog. When a certificate renews, the switch doesn't install it automatically. Someone has to import the new certificate, assign it to every service that uses it, and save the configuration.

That means repeating the process on every switch, every time a certificate expires. With certificate lifetimes shrinking to 47 days, that's a lot of maintenance.

CertKit renews certificates centrally, then the CertKit Agent installs them on each switch through the AOS-CX REST API. It verifies the certificates, assigns them to the services you choose, and saves the configuration. No manual certificate handling required.

Start free trial Watch demo

Built for Aruba AOS-CX

A ready-to-use Aruba AOS-CX deployment template is included in every CertKit account. No scripting required.

On every renewal, the agent connects to the switch's REST API, makes sure the issuing root certificate is trusted, and imports the new certificate under a name it manages. It verifies the SHA-256 fingerprint of the certificate and every certificate in its chain, assigns the new certificate to the services you selected, removes older CertKit certificates that are no longer in use, and saves the configuration.

Updating the web interface certificate briefly restarts HTTPS on the switch. The agent waits for the web interface to come back online, then signs in again. You can schedule deployments for a maintenance window, so renewals happen at 2am Sunday instead of interrupting someone working in the switch's web interface.

How to install an SSL certificate on an Aruba AOS-CX switch

Here's what you have to do manually when managing certificates yourself:

  1. Add the root CA. Create a trust anchor profile with crypto pki ta-profile and paste in the root certificate of the certificate authority (CA) that will sign your certificate.
  2. Create the certificate request. Create a certificate entry with crypto pki certificate, set the subject, and generate a certificate signing request (CSR). Submit it to your CA. A wildcard certificate can cover every switch in the stack.
  3. Import the signed certificate. Paste the signed certificate and its intermediate certificates back into the same certificate entry, or import the certificate with its private key if your CA generated the request.
  4. Assign it to each service. Run crypto pki application https-server certificate with the certificate name, and repeat for the captive portal, RadSec, syslog, or any other service that uses it.
  5. Save the configuration on every switch. Run write memory, or the next reboot will bring back the old certificate. Then repeat the process on the next switch.

Every one of these steps is manual, and the switch won't repeat them when the certificate renews. With certificate lifetimes shrinking to 47 days, you'll be doing this about twelve times a year, on every switch. Miss the RadSec certificate and the switch can't communicate with ClearPass to authenticate people connecting to your network.

That's a lot of repetitive work, and a lot of opportunities for something to go wrong. At 47 days, automating certificate management is the only sustainable way to run AOS-CX certificates.

Here's how CertKit handles the entire process.

CertKit makes what many companies struggle with much easier to manage while at the same time providing great value compared to the traditional vendors in the space.

Ben Story, Managed Services Director, RedEye Network Solutions

How it works

 Your network             CertKit                 ACME CA
┌───────────────────┐     ┌──────────────────┐    ┌─────────────┐
│  ┌─────────────┐  │     │                  │    │             │
│  │CertKit Agent├──┼────►│  Issue & Renew   │◄──►│             │
│  └──────┬──────┘  │     │   Certificates   │    │             │
│         │ REST    │     │                ┌───┐  └─────────────┘
│         │ API     │     └────────────────│DNS│
│         ▼         │                      └───┘
│  ┌─────────────┐  │
│  │ AOS-CX      │  │
│  │ [x] Imported│  │
│  │ [x] Assigned│  │
│  │ [x] Saved   │  │
│  └─────────────┘  │
└───────────────────┘

CertKit handles certificate issuance and renewal centrally using delegated DNS validation. You add a one-time CNAME record to your domain, and CertKit handles the DNS challenges required for every renewal after that.

The CertKit Agent runs on a Windows host on your management network. It pulls each renewed certificate from CertKit over outbound HTTPS, then connects to each switch's REST API using a switch administrator account.

The switch password is stored encrypted in CertKit. The switches never connect to CertKit, and CertKit never needs to connect into your network. The agent handles communication with the switches from inside your network. One agent can manage every switch it can reach.

The services you can assign

Choose which services should use the renewed certificate by listing them in the deployment, separated by commas. The services must already be enabled on the switch. Available services depend on the switch model. Use import-only if you want to install the certificate without assigning it to any services.

https-server Web interface and REST API captive-portal Guest and onboarding redirects radsec-client RADIUS over TLS to ClearPass or another server syslog-client Syslog over TLS dot1x-supplicant The switch's own 802.1X identity est-client EST enrollment hsc Hardware switch controller connection

What CertKit handles

Setup takes about ten minutes

Once your network is ready, getting automated certificate deployment running is straightforward:

  1. Connect your domain. Add a one-time CNAME record to delegate DNS validation to CertKit.
  2. Enable the REST API. Turn on HTTPS REST access in read-write mode on each switch. Use an account in the built-in administrators group.
  3. Install the CertKit Agent. Run one command on a Windows host that can reach the switches' management addresses.
  4. Configure the AOS-CX deployment. Choose the Aruba AOS-CX template, then enter the switch address, account credentials, and the services you want to update.

See the full architecture →

Aruba AOS-CX deployment requirements and troubleshooting →

Why saving the configuration is the tricky part

On AOS-CX, certificate changes are part of the running configuration. If a script imports and assigns a certificate but never saves the configuration, the switch serves the new certificate until its next reboot. After rebooting, it goes back to the old certificate, which might already be expired.

But saving has its own catch. The switch saves the entire running configuration, not just the certificate changes. That means any unrelated changes someone left unsaved will be saved too.

CertKit only saves when the deployment actually changes something, and records the save in the deployment log. To avoid accidentally saving unrelated work, keep unsaved changes off the switch during the deployment window. If a deployment fails, check the switch before running it again.

AOS-CX is just one part of your Aruba network

Most Aruba networks have more than one place where TLS certificates need attention. You might have Aruba ClearPass on the other end of RadSec, Aruba Mobility Controllers handling wireless, and the Aruba Central certificate store to manage.

Certificates also live on the firewalls at your network edge, including Juniper SRX and FortiGate. CertKit automates certificate deployment across all of them from one account.

See all integrations

Start automating AOS-CX certificates today

Free 30-day trial. No credit card required. Direct access to our engineering team to get you set up.

Start free trial See pricing