Skip to content

← All integrations

Load balancer

Uploads certificates and switches the bindings of LoadMaster's virtual services.

The appliance runs the package and connects to Kemp LoadMaster through REST API v2 over HTTPS on port 443. No agent is installed on Kemp LoadMaster.

What happens

  1. The appliance connects to Kemp LoadMaster through REST API v2 on port 443.
  2. The package takes a backup and uploads the certificate, key and any intermediate.
  3. 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.
  4. Verification: the package checks through the API that the certificate exists and is bound. Test TLS against the service yourselves.

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 7.2 and later
Actions
Discovery, Installation, Verification, Rollback, Removal
Packages
kemp-loadmaster
Note
  • 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.
  • The removal action unbinds the certificate from every virtual service and can delete it from LoadMaster.

Get started