Kemp LoadMaster
Copy link to the page “Kemp LoadMaster”Installs certificates on selected LoadMaster virtual services or management through REST API.
What happens
- The appliance connects to Kemp LoadMaster through REST API v2 on port 443.
- The integration imports certificate, key and missing intermediates under their own names. It is bound to selected virtual services or management; previous certificates remain.
- CertFile, SSL state and management certificate are read back. The TLS leaf is checked where reachable; KEMP_SERVED_CHECK can require served confirmation.
Technical details
- Connection
- The integration runs on the appliance, which connects over HTTPS to REST API v2, port 443. No service agent is installed.
- Service ports
- 443
- What you need
- Certificates & Security > Remote Access: tick Enable API Interface. System Configuration > System Administration > User Management: add a local user, click Modify and grant Certificate Creation, Intermediate Certificates and Virtual Services. On the same page click Generate New APIKey under API Keys and paste the key here.
- Platform
- LoadMaster LMOS 7.2.50+, REST API v2
- Actions
- Discovery, Installation, Verification, Rollback, Removal
- Integrations
-
kemp-loadmaster2.0.0 - Note
-
- Restoration and rollback use previous_state and preserve later bindings. Stored certificates are not deleted. Undeploy only removes certificates from selected virtual service bindings and does not disable SSL. Native ACME accounts remain. 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.