Skip to content

← All integrations

Identity and remote access · Web server

Renews HTTPS, RADIUS and RadSec certificates on one selected ClearPass node.

The appliance runs the integration and connects to Aruba/HPE ClearPass through ClearPass Policy Manager REST API over HTTPS on port 443. No service agent is installed on Aruba/HPE ClearPass.

What happens

  1. The appliance connects to Aruba/HPE ClearPass through ClearPass Policy Manager REST API on port 443.
  2. Select one cluster node and HTTPS, RADIUS or RadSec roles. Certificate, key and intermediates become an encrypted PKCS#12 held in memory.
  3. The node fetches the certificate and key as PKCS#12 from a temporary HTTP listener on the appliance or the server running the service agent. RADIUS and RadSec change before HTTPS; RSA and EC have separate HTTPS roles.
  4. Roles are read back and HTTPS is checked over TLS. RADIUS is confirmed through the API without an EAP exchange; the RadSec probe is informational.

Technical details

Connection
The integration runs on the appliance, which connects over HTTPS to ClearPass Policy Manager REST API, port 443. No service agent is installed.
Service ports
443
What you need
Guest > Administration > API Services > API Clients: create a client with grant type client_credentials and an operator profile that may change platform certificates (Super Administrator). Enter its client ID and secret here, and the address of the ClearPass node. ClearPass fetches the certificate from the appliance or the server running the service agent over HTTP; that machine must be reachable from the node (use a service agent on a server in ClearPass's network or CLEARPASS_FETCH_ADDRESS).
Platform
ClearPass Policy Manager REST API 6.14
Actions
Discovery, Installation, Verification, Rollback
Integrations
aruba-clearpass-api 1.0.0
Note
  • Automatic restoration needs the previous certificate and matching key as inputs. One previous pair must suit every selected role. Rollback uses deploy’s state and the material to restore; later role changes are preserved. The certificate chain consists of the intermediate certificates that link the server certificate to a root certificate the browser trusts. ACME is the protocol a CA uses to issue certificates automatically.
  • CLEARPASS_FETCH_ADDRESS selects an address and optional port reachable by the node. The integration keeps no backup files. CEM settings and individual RADIUS service certificates are unchanged.

Certificate requirements

ClearPass has separate HTTPS(RSA) and HTTPS(ECC) roles and a RADIUS/EAP server certificate per node. The integration’s key choices are RSA 2048, 3072 or 4096 bits and ECDSA P-256 or P-384. The API’s CSR menu also includes EC 521 bits; 4096 and 521 are the largest documented CSR choices, not documented external-import maxima. The ClearPass 6.11 evaluated TLS configuration describes RSA 2048/3072/4096 and EC P-256/P-384. Public import sources specify no general minimum or maximum key size for each role.

Common Name (CN) is required when creating a CSR in ClearPass. The sources do not establish whether CN is mandatory for an externally issued server-certificate import. ACME is the protocol a CA uses to issue certificates automatically. Compatibility with CN-less ACME profiles such as tlsserver and minimal is therefore undocumented. Use SANs matching the guest portal hostname and the clients’ EAP server-validation policy.

Use a server certificate for server authentication (serverAuth EKU). The checked import sources specify no mandatory clientAuth EKU or keyEncipherment KU for the HTTPS or RADIUS/EAP server certificate. The CEM guide’s clientAuth requirement applies to the certificate authenticating the EST client to its issuer, not the deployed server certificate. EAP clients have their own requirements; an unpublished import constraint is no guarantee of acceptance by every client or minimal profile.

Aruba discourages wildcard CN and EV certificates for RADIUS/EAP because some clients cannot authenticate with them. This is a recommendation, not a documented import ban. CEM can generate DNS and IP SANs; the checked sources specify no SAN-count maximum or general external-import IP-SAN rule. HTTPS and EAP server names must match the selected service and client configuration.

The ClearPass 6.12 import dialog accepts a certificate with a saved key, a PKCS#12 file (.pfx/.p12), or separate certificate and key files. P7b Base64 chains are unsupported for HTTPS and RADIUS/EAP. The role API in the checked 6.11 and 6.14.1 definitions fetches a certificate or PKCS#12 from a URL; new external keys are supplied in password-protected PKCS#12. The dialog specifies no PEM/DER limits, and JKS import is undocumented.

The checked sources publish no version-specific PFX import rule for AES versus 3DES/RC2 encryption. An example does not establish an AES ban. The API sends the PFX passphrase in the request body. The 6.12 guide specifies the cluster password for cluster PKCS#12 imports; the sources do not establish that arbitrary passphrases work on every cluster version. Staging URLs must contain no login, token or password.

A certificate chain is the intermediate certificates that link the server certificate to a root the browser trusts. Supply the server certificate with its matching private key and required intermediates. Import sources specify no mandatory chain order or root inclusion. The integration can place the leaf first, followed by intermediates toward the issuer; this is not a documented ClearPass requirement. A PKCS#12 server-certificate export contains the certificate, intermediates and private key. Certificate API readback provides no documented private key for rollback.

The role API selects the destination by node UUID and role name. The checked sources specify no PFX friendly-name or alias requirements, including characters or maximum length. A JKS alias must not be introduced as a ClearPass requirement.

Use a certificate valid at deployment time. The checked sources specify no ClearPass minimum or maximum validity period for external imports. Public CA rules and client validation apply separately and must not be described as a ClearPass import limit.

Next steps