6.5.36 Aruba Central
API clients, minimum roles, and a stable certificate name
CertKit has two templates for the HPE Aruba Networking Central certificate store, one for Classic Central and one for the new Central. Both upload the certificate, private key, and chain as a server certificate under the name you choose. The first deployment creates it, and every renewal updates the same name.
Only the certificate store changes. The templates don’t edit groups, profiles, devices, or certificate assignments, and they don’t check whether devices have picked up the renewal. Assign the certificate in Central after the first deployment.
| Template | Sign-in | Key type | Certificate name |
|---|---|---|---|
| Aruba Central (Classic): Certificate Store | Classic API Gateway app token plus a Central user with a password | RSA | Any name except the vendor default |
| Aruba Central (New): Certificate Store | Personal API client from HPE GreenLake | RSA or EC | 20 characters at most |
Both templates run on a Windows CertKit agent with outbound HTTPS to your region’s Central API. No extra PowerShell modules are needed.
Classic Central
Create an app token in Central under Organization > Platform Integration > REST API > My Apps & Tokens > Add Apps & Tokens. You’ll need its client ID and secret, your customer ID (click the user icon at the top right of Central), and a Central user that signs in with a password, not SSO.
That user needs two roles, assigned in HPE GreenLake:
- The built-in Aruba Central View Only role.
- A custom role with the Edit Classic NMS service configuration permission (
aruba-central.nms.configuration.edit).
Set Classic API Gateway URL to your region’s gateway from Organization > Platform Integration > REST API, for example https://app1-apigw.central.arubanetworks.com. A portal URL doesn’t work.
The agent saves the refresh token Central issues, encrypted for the agent’s Windows account, under %ProgramData%\CertKit\certkit-agent\aruba-central-classic. Central can throttle new token requests, and the template doesn’t retry them.
New Central
Create a personal API client in HPE GreenLake under Manage Workspace > Personal API clients > Create personal API client. Pick your Central instance as the service manager, not HPE GreenLake Platform. GreenLake shows the client secret only once. If it’s lost, reset it there.
The API client acts with the rights of the user who created it. That user needs:
- The built-in Aruba Central View Only role.
- A custom role with the Manage certificates permission (
aruba-central.service.certificate-management.readwrite). Without it, Central refuses the upload with HTTP 403.
Set Central API base URL from Menu > API Gateway > REST API in Central, for example https://us1.api.central.arubanetworks.com. The Classic gateway (apigw) doesn’t work with this template.
HPE lists the new Central configuration APIs as alpha with select availability, so your account may need to be allow-listed before the upload works.
Keep the certificate name
Usages in Central refer to the certificate by name. Keep Certificate name in Central the same for every renewal, so nothing has to be re-pointed. When Central’s checksums for that name already match the certificate, key, and chain, the deployment skips the upload. After an upload, it compares Central’s checksums with the bundle it sent.
Writes aren’t retried or rolled back. Keep the previous certificate, key, and chain until your devices are confirmed on the new one.
Common problems
- “Use an official Classic HTTPS API Gateway URL”: the Classic template got a portal URL. Use the gateway URL from the REST API page.
- “Use the new Central API base URL”: the new Central template got a Classic gateway or portal URL.
- “Check the client ID and secret”: for the new Central, also confirm the API client was created for the Central instance, not for the HPE GreenLake platform.
- HTTP 403 on upload: the user is missing the custom role with the certificate permission.
- “Central limits certificate names to 20 characters”: shorten Certificate name in Central for the new Central.
- Devices still use the old certificate: check that the usage or profile points at the same certificate name the deployment updates.
For a product overview, see certificate automation for Aruba Central.