What BIG-IP does on its own
BIG-IP 21.1.0 added ACMEv2 support. F5 lists it in the new features in BIG-IP 21.1.0, with providers including Let’s Encrypt, ZeroSSL, DigiCert, Buypass, Google Trust Services and SSL.com. F5 DevCentral guides describe a virtual server listening on port 80 with the ACMEv2 challenge option enabled, which means the HTTP-01 challenge.
Many estates still run earlier versions, which have no built-in ACME client. For those, the common route is a script. F5’s DevCentral describes kojot-acme, the dehydrated ACME client adapted for BIG-IP, run on a schedule. That article notes that by default the script does not place the new certificate into an SSL profile.
What a safe rotation looks like
Whatever obtains the certificate, rotating it on BIG-IP has the same steps:
- Import the certificate, key and chain as new objects, with a name that includes the expiry date, rather than overwriting the ones in use.
- Update each client SSL profile that uses the old certificate to use the new one.
- Save the configuration, and sync it to the other members of the device group.
- Check that each virtual server serves the new certificate before you delete the old objects.
Overwriting the objects in place is quicker, but it leaves no simple way back if the new chain is wrong.
Where it gets hard
- Profiles and virtual servers. One certificate may be used by several client SSL profiles, and missing one leaves a virtual server on the old certificate.
- HA and device groups. A change that is not synced leaves the standby unit with an expiring certificate after a failover.
- Challenges. HTTP-01 needs the name to reach a virtual server on port 80. Wildcards and internal-only names need DNS-01 instead.
- Version spread. A fleet on several BIG-IP versions cannot rely on one built-in feature.
Shorter certificate lifetimes, covered in certificate lifetimes are falling to 200, 100 and 47 days, turn each of these into a monthly job.
How clm.mt handles BIG-IP
clm.mt renews the certificate with DNS-01, imports it through the iControl REST API, updates the client SSL profiles that use it, saves the configuration and can undo the change. The served certificate is then checked.
clm.mt status
Preview for F5 BIG-IP. 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
- FortiGate ACME certificates and automatic renewal
- IIS SSL certificate auto renewal on Windows Server
- Kubernetes certificate management and TLS Secret renewal
- NetScaler ADC SSL certificate renewal and update
- NGINX SSL certificate auto renewal with ACME
- Palo Alto firewall certificate renewal automation