What NetScaler does on its own
On NetScaler ADC, a certificate and its key are a certkey object, bound to virtual servers or services. The ADC itself has no general ACME client. Automated renewal is offered through NetScaler Console: its documentation on automated certificate renewal by using the ACME protocol describes Console acting as the ACME client, with Let’s Encrypt and DigiCert as the supported certificate authorities and minimum ADC builds per release.
Without Console, administrators use community tools. Examples are the GenLeCertForNS PowerShell script, which requests Let’s Encrypt certificates and adds or updates them on the ADC, and hooks that drive the NITRO API from an ACME client.
Updating a certificate in place
The usual way to renew on NetScaler is to update the existing certkey rather than create a new binding:
- Upload the new certificate and key files to the appliance.
- Update the certkey to point at the new files. The bindings on virtual servers stay as they are.
- Link the certkey to its intermediate certificate, so clients receive the full chain. Do not include the root.
- Save the configuration. On an HA pair, check that the change reached the secondary node.
- Check the served certificate on each virtual server that uses it.
If the new certificate has different names from the old one, the update is refused unless you tell NetScaler to skip its domain check, so review the names before you force it.
Where it gets hard
- Chains. A certkey that is not linked to the right intermediate serves an incomplete chain, which some clients reject.
- Unsaved changes. An update that is not saved is lost when the appliance restarts.
- Shared certkeys. One certkey may be bound to many virtual servers, so a wrong update affects all of them.
- Lifetimes. As public certificates move toward 47 days, explained in certificate lifetimes are falling to 200, 100 and 47 days, manual updates stop being practical.
How clm.mt handles NetScaler
clm.mt renews the certificate with DNS-01 and uses the NITRO API: it uploads the files, adds the certkey or updates it in place, reuses and links the intermediate certificate, leaves out the root, saves the configuration, and rolls back if the save fails. It will not replace a different certificate that is already bound to a virtual server.
clm.mt status
Preview for NetScaler ADC. Contract-tested APIs. Appliance models and firmware need customer-specific acceptance. See the integrations board for every tested scope, and the documentation to plan a pilot.
Other platform guides
- AD CS certificate autoenrollment and auto renewal
- AWS load balancer certificate renewal with ACM
- Azure Key Vault certificate auto renewal, and when it does not happen
- F5 BIG-IP SSL certificate renewal automation
- FortiGate ACME certificates and automatic renewal
- IIS SSL certificate auto renewal on Windows Server
- Kubernetes certificate management and TLS Secret renewal
- NGINX SSL certificate auto renewal with ACME
- Palo Alto firewall certificate renewal automation