Built for Aruba Central
Pre-built templates for Classic Central and the new Central ship in your CertKit account. No scripting required.
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.
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.
The manual process, if you want to do it yourself:
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
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.
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.
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.
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.
Free 30-day trial. No credit card required. Direct access to our engineering team to get you set up.