6.5.11 F5 BIG-IP

Pick the Client SSL or Server SSL template and update the intended profile

CertKit has three F5 BIG-IP templates. Each uploads the PEM certificate and private key through iControl REST, repoints an existing SSL profile to them, and saves the running configuration.

Template Agent Updates
F5 BIG-IP: SSL Client Profile (REST API) Windows or Linux A Client SSL (client-ssl) profile. This is the certificate a virtual server presents to browsers and other clients.
F5 BIG-IP: SSL Server Profile (REST API) Windows A Server SSL (server-ssl) profile. This is the certificate the BIG-IP presents to backend pool members that ask for a client certificate.

The Client SSL template exists in a Windows version and a Linux version with the same name and settings.

watch F5 BIG-IP auto-renewal

When you need the Server SSL template

When a virtual server re-encrypts traffic to its pool members, the Server SSL profile controls the BIG-IP side of that connection. If a backend requires mutual TLS, it asks the BIG-IP for a client certificate, and the BIG-IP sends the certificate and key set on the Server SSL profile. The Server SSL template replaces that certificate and key.

It does not change the profile’s CA file or any other setting the BIG-IP uses to validate the certificate the backend sends. If your backends never ask for a client certificate, the Server SSL profile’s certificate isn’t used and you don’t need this template.

A backend that checks client certificates usually requires the TLS client authentication extended key usage. Public CAs are phasing out client authentication certificates, and Let’s Encrypt stopped issuing them in 2026. Issue this certificate from CertKit Private PKI with client authentication key usage, and make sure the backend trusts that CA.

Requirements

  • The agent host must reach the BIG-IP management interface over HTTPS.
  • The BIG-IP account must be allowed to upload and delete SSL certificate and key files, modify the target profile type (client-ssl or server-ssl), and save the configuration.
  • The target profile must already exist. The templates don’t create profiles.
  • Use the administrative partition that contains the profile. The default is Common.

The templates tolerate a self-signed certificate on the BIG-IP management interface.

Template settings

Setting Requirement
F5 management IP/host and port Management address, including a port other than 443, such as 10.1.2.3:8443.
F5 username Account with the SSL file and profile permissions above.
F5 password The password for that account.
F5 partition Partition that contains the profile. Most setups use Common.
SSL Client profile name Client SSL template. The existing client-ssl profile that should use the renewal.
SSL Server profile name Server SSL template. The existing server-ssl profile that should use the renewal.

What each run does

  1. Reads the profile and notes the certificate, key, and chain it uses now.
  2. Uploads the certificate, with its intermediates, and the private key. It creates SSL certificate and key objects named after the profile plus a Unix timestamp, such as /Common/my-profile-1760450000.crt. A BIG-IP won’t replace a file that a profile is using, so each renewal gets a new name.
  3. Repoints the profile to the new objects and sets its separate chain to none, because the uploaded certificate already includes the intermediates.
    • Client SSL: writes one Certificate Key Chain entry named default. This replaces the profile’s whole Certificate Key Chain list.
    • Server SSL: sets the profile’s Certificate and Key.
  4. Deletes the certificate, key, and chain objects the profile used before step 3. Delete errors are ignored, so an object that another profile still uses stays in place.
  5. Saves the running configuration so the change survives a reboot.

The templates don’t start a config sync. If your device group syncs manually, sync it after a deployment.

Before the first run

Step 4 deletes whatever the profile referenced before, whether or not CertKit uploaded it. On the first run, that is the certificate, key, and chain you installed by hand. Export a copy first if you want to keep them.

A Client SSL profile that holds more than one certificate, such as an RSA and an ECDSA pair, keeps only the CertKit certificate after a run. Use a separate profile for the other key type.

Common problems

  • Profile not found: confirm the profile name, the partition, and the template. A Server SSL profile name in the Client SSL template fails, and the reverse fails too.
  • Authorization failure: confirm the account can manage SSL files and profiles, not only view them.
  • Certificate imported but traffic is unchanged: confirm the profile is attached to the active virtual server. For a Server SSL profile, also confirm the backend asks for a client certificate.
  • Backend rejects the BIG-IP’s certificate: the certificate lacks the client authentication key usage, or the backend doesn’t trust its CA. See When you need the Server SSL template.
  • A second certificate disappeared from a Client SSL profile: the template replaced the Certificate Key Chain list. Move the other key type to its own profile.
  • Old certificate still listed on the BIG-IP: another profile still uses it, so the delete failed. Remove it by hand once nothing references it.
  • Management connection failure: include the management port when it is not 443 and confirm network access from the agent host.

For a product overview, see certificate automation for F5 BIG-IP.