Create a Kemp Virtual LoadMaster machine¶

Create a Kemp Virtual LoadMaster machine so Certificate Manager - SaaS can discover the certificates on a Kemp LoadMaster and provision certificates to its virtual services. Certificate Manager - SaaS connects to the LoadMaster's API through a VSatellite.

To create a Kemp Virtual LoadMaster machine¶

1. Sign in to Certificate Manager - SaaS.
2. Click Installations > Machines.
3. Click New, and then select Kemp Virtual LoadMaster.
4. On the Properties step, in Name, enter a name for the machine.
5. For Owning Team, choose the team that owns the machine. System Administrators and PKI Administrators can choose any team. Resource Owners can choose only a team they own or belong to.

6. For VSatellite, choose a VSatellite that can reach the machine. A VSatellite that's the primary of a high availability group shows its number of active replicas, and Certificate Manager - SaaS can run the machine's operations on any healthy VSatellite in the group.

7. In Kemp LoadMaster Address/Hostname, enter the hostname or IP address of the Kemp LoadMaster.

8. (Optional) In Port, enter the management port if it isn't 443. If you leave it empty, Certificate Manager - SaaS uses 443.

9. For Credential Type, choose how to provide the credentials:

   • Enter Credentials to enter the credentials in the next step. This is the default.
   • Select Credentials to use shared credentials from a credential manager integration. Then, for Credential, choose the credential.

   Note

   Select Credentials requires the credential manager capability, which requires additional licensing. Without it, Credential shows No credentials are available. System Administrators and PKI Administrators can choose any credential. Resource Owners can choose only the credentials that belong to their teams.

10. If you chose Enter Credentials, enter the Username and Password of the Kemp LoadMaster account. If you chose Select Credentials, the stored account needs the same access.

    Note

    Certificate Manager - SaaS encrypts the credentials you enter and doesn't display them again. On the machine's Properties tab, they appear masked. To keep a stored credential when you edit the machine, leave its masked value unchanged. Keep your own secure record of the credentials in case you need them again.

11. Click Test Access. After the connection succeeds, click Continue. The Discovery step opens.

    Note

    A successful test confirms that Certificate Manager - SaaS can sign in to the Kemp LoadMaster API and list its certificates. It doesn't confirm that the account can add certificates or modify virtual services, which provisioning needs.

12. (Optional) To skip certificates that have already expired, enable Exclude expired certificates.

13. (Optional) To skip certificates that no virtual service uses, enable Exclude certificates that are not in use by a virtual service.

    Discovery reads every certificate on the Kemp LoadMaster and records the virtual services that use each one.

14. (Optional) To discover certificates on a schedule, enable Schedule. For Repeat every, choose Day, Week, or Month, and then in At, enter the time. For Week, select the days of the week. For Month, enter the days in Day of month. Times are in Coordinated Universal Time (UTC).

15. Click Continue. The Provisioning step opens.

16. (Optional) To provision certificates on a schedule, enable Schedule. For Repeat every, choose Day, Week, or Month, and then in At, enter the time. For Week, select the days of the week. For Month, enter the days in Day of month. Times are in Coordinated Universal Time (UTC).

    Scheduled provisioning pushes only certificates that are queued for deployment, such as renewed certificates, so renewals install during the window you choose.

17. Click Finish.

What's next?¶

After you create the machine, provision a certificate to it. You can also run discovery on the machine at any time to track the certificates on your LoadMaster.