Kemp LoadMaster
Copy link to the page “Kemp LoadMaster”
Uploads certificates and switches the bindings of LoadMaster's virtual services.
What happens
- The appliance connects to Kemp LoadMaster through REST API v2 on port 443.
- The package takes a backup and uploads the certificate, key and any intermediate.
- The certificate is bound to the virtual services and put into use. If it fails: Rollback puts the bindings and the management certificate back. The certificate store is not restored.
- Verification: the package checks certificate content, its position in the selected services and the certificate each service serves over TLS.
Technical details
- Connection
- The package runs on the appliance, which connects over HTTPS to REST API v2, port 443. No agent is installed.
- You need
- Management IP or host name and an API key from System Configuration › API Authentication.
- Platform
- LoadMaster LMOS 7.2.50 and later
- Actions
- Discovery, Installation, Verification, Rollback, Removal
- Packages
-
kemp-loadmaster1.8.0 - Note
-
- Management TLS is verified by default. Use system trust, a CA bundle or the SHA-256 fingerprint of the whole certificate. A mismatch stops the connection before the API key is sent. Existing Kemp trust settings remain supported.
- When deployment changes the management certificate, it accepts only the previous and exact new certificate for that run. Update a saved fingerprint to the new certificate before the next run.
- Discovery finds virtual services, installed certificates and intermediate certificates. Deployment can also replace the management certificate.
- Rollback needs the installation's backup, so keep it until you no longer want to roll back. Rollback refuses, without changing anything, a renewal in place and a state that has changed since the installation.
- Removal unbinds the certificate only from the selected virtual services. SSL stays enabled and the management certificate and certificate store are preserved.