F5 BIG-IP
Copy link to the page “F5 BIG-IP”Installs the certificate and key, repoints client-ssl profiles and syncs HA.
What happens
- The appliance connects to F5 BIG-IP through iControl REST on port 443.
- The integration imports separate certificate, key and chain objects. Selected client-ssl profiles receive the new identity for the same key type; the other key type and previous objects remain.
- Configuration is saved and config-synced in a sync-failover group. Profiles are read back and their virtual servers checked over TLS where possible.
Technical details
- Connection
- The integration runs on the appliance, which connects over HTTPS to iControl REST, port 443. No service agent is installed.
- Service ports
- 443
- What you need
- System > Users > User List > Create: enter a user name and password, set Role to Administrator (it covers all partitions) and leave Terminal Access disabled. Click Finished and enter the username and password here.
- Platform
- BIG-IP LTM 13.1+, iControl REST
- Actions
- Discovery, Installation, Verification, Rollback, Removal
- Integrations
-
f5-bigip-api2.0.0 - Note
-
- Rollback uses PREVIOUS_BINDINGS and CERT_OBJECT from deploy and preserves later profile changes. New objects remain until undeploy. A shared profile affects all its virtual servers; native ACME orders remain on BIG-IP. 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.