← Integrations

Automated SSL certificate renewal for Aruba Central

Keep the certificate name in Aruba Central. Replace the certificate.

Aruba Central assigns SSL certificates by name. Upload a renewal under a different name and your captive portal or RadSec profile still points to the old certificate. With public certificate lifetimes heading to 47 days, you'll be replacing those certificates more often.

CertKit renews the certificate and uploads it to the certificate store under the same name. There are templates for both Classic and new Aruba Central.

Start free trial Watch demo

Built for Aruba Central

Pre-built templates for Classic Central and the new Central ship in your CertKit account. No scripting required.

On every renewal, the agent signs in to the Central API and uploads the certificate, private key, and chain as a server certificate under the name you chose. The first run creates it. Every renewal after that updates the same name, so anything in Central that uses the certificate keeps pointing at it. When the bundle in Central already matches, the agent skips the upload.

After the first upload, assign the certificate in Central. On later renewals, CertKit verifies the updated bundle in the certificate store. Central handles delivery to the devices assigned to it.

How to upload an SSL certificate to Aruba Central

The manual process, if you want to do it yourself:

  1. Create a certificate request. Generate the private key and CSR with OpenSSL or your CA's tools. Keep the key, because Central needs it with the certificate.
  2. Get the certificate signed. Submit the CSR to a certificate authority and download the certificate and its chain. Combine them with the key into one PEM or PKCS12 file for the upload.
  3. Upload it to the certificate store. In Classic Central, set the filter to Global, go to Maintain → Organization → Certificates, and add it as a Server Cert in PEM, DER, or PKCS12 with its passphrase. In the new Central, open Certificate Management from the menu and click Add.
  4. Assign the certificate. Point the captive portal, RadSec, or other usage at the certificate by name in the group or profile configuration, then let Central push it to the devices.
  5. Replace it when it renews. Upload the renewal to the same certificate name so the assignments carry over. A new name means re-pointing every place that used the old one.

With public certificate lifetimes shrinking to 47 days, renewing a few weeks early means repeating this work about twelve times a year. If the captive portal certificate expires, guests can see a browser warning before they can join Wi-Fi.

At 47 days, automation is the only sustainable way to run Aruba Central certificates. Here's how CertKit does it.

CertKit has been a fantastic solution for automating our environment’s SSL/TLS certificates. With a single pane of glass for centralized management, visibility, and monitoring and the highly customizable interface for granular control over individual systems, we have found great value in reducing the time and complexity of managing an ad-hoc ACME solution for individual certificate automation.

Seth Allums, Lead Systems and Information Security Engineer, Clackamas Community College

How it works

 Your network            CertKit                 ACME CA
┌───────────────────┐     ┌──────────────────┐    ┌─────────────┐
│  ┌─────────────┐  │     │                  │    │             │
│  │CertKit Agent├──┼────►│  Issue & Renew   │◄──►│             │
│  └──────┬──────┘  │     │   Certificates   │    │             │
│         │         │     │                ┌───┐  └─────────────┘
└─────────┼─────────┘     └────────────────│DNS│
          │ REST API                       └───┘
          ▼
┌───────────────────┐
│  Aruba Central    │
│  [x] Uploaded     │
│  [x] Checksums    │
└───────────────────┘

CertKit issues and renews certificates centrally using delegated DNS validation. You create a one-time CNAME record, and CertKit handles every ACME challenge after that.

The CertKit Agent runs on a Windows host. It pulls each renewal from CertKit over outbound HTTPS, then calls your region's Central API gateway with an API client you create for it. The API credentials are stored encrypted in CertKit. CertKit never connects into your network.

Classic Central and the new Central

HPE runs two versions of Central with different APIs and sign-in, so CertKit has a template for each. Pick the one your account uses.

Aruba Central (Classic) Classic API Gateway app token and a password-based Central user. RSA certificates Aruba Central (New) Personal API client from HPE GreenLake. RSA or EC certificates, names up to 20 characters

What CertKit handles

Setup takes about ten minutes

  1. Connect your domain. Add a one-time CNAME record to delegate DNS validation to CertKit.
  2. Create API access. For Classic Central, add an app token under Organization → Platform Integration → REST API, and use a Central user that signs in with a password. For the new Central, create a personal API client in HPE GreenLake for your Central instance. Either way, the user needs the Aruba Central View Only role plus a custom role with the certificate write permission for that version of Central.
  3. Install the CertKit Agent. One command on a Windows host with outbound HTTPS.
  4. Add the Aruba Central deployment script. Choose the Classic or new Central template, then enter the API URL, the credentials, and the certificate name.

See the full architecture →

Aruba Central deployment requirements and troubleshooting →

Why the certificate name matters

In Central, usages and profiles refer to a certificate by its name. Upload a renewal under a new name and every reference still points at the old certificate until someone finds them all and switches them. The old one expires on schedule regardless.

CertKit always writes to the name you set in the deployment, so the reference never moves. Pick it once, keep it short (the new Central allows 20 characters), and every renewal lands in the same place.

Central is just one part of your Aruba network

Most Aruba networks have more than one place where TLS certificates live: Aruba ClearPass for policy and RADIUS, Aruba Mobility Controllers for the WebUI and captive portal, Aruba AOS-CX switches, and Cisco ISE doing the same RADIUS job in other networks. CertKit automates all of it from one account.

See all integrations

Start automating Aruba Central 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