docs/documentation/platform/pki/applications/certificate-syncs/kemp-loadmaster.mdx
Deploy certificates to Progress Kemp LoadMaster load balancers via the RESTful API. Certificates can be automatically bound to a Virtual Service for seamless load balancer integration.
<Info> Certificate Syncs are configured per Application. First select which certificates to sync, then configure the Kemp LoadMaster destination. </Info> 2. Select the **Kemp LoadMaster** option.
3. Configure the **Destination**:
- **Kemp LoadMaster Connection**: The connection to authenticate with.
- **Virtual Service** (Optional): Select the Virtual Service to bind the certificate to from the list fetched from the LoadMaster (shown as name and VIP:port). Leave unset to only import the certificate without binding.
4. Configure the **Sync Options**:
- **Enable Removal of Expired/Revoked Certificates**: Remove certificates from the destination if they are no longer active.
- **Preserve Certificate on Renewal**: When a certificate is renewed, keep using the original certificate's identifier on the LoadMaster instead of generating a new name from the schema. This preserves the entry and any Virtual Service binding, and matters when your name schema is certificate-specific (for example it includes `{{certificateId}}`, which changes on renewal).
- **CA Certificate Name Schema**: Controls how each certificate's chain (intermediate CA certificates) is named in the LoadMaster's Intermediate Certs store, using the `{{fingerprint}}` and `{{commonName}}` placeholders. Defaults to `Infisical-ca-{{fingerprint}}`.
- **Certificate Name Schema**: Customize certificate identifiers using placeholders such as `{{certificateId}}`, `{{commonName}}`, `{{profileId}}`, and `{{applicationId}}`. Must include `{{certificateId}}` or `{{shortCertificateId}}`. Defaults to `Infisical-{{certificateId}}`. See [Certificate Name Schema](/documentation/platform/pki/applications/certificate-syncs/overview#certificate-name-schema) for the full placeholder reference.
- **Auto-Sync Enabled**: Automatically sync certificates when changes occur.
5. Configure the **Details**:
- **Name**: The name of your sync (slug-friendly).
- **Description**: Optional description.
6. Select which certificates should be synced.
7. Review and click **Create Sync**.
</Tab>
<Tab title="API">
To create a **Kemp LoadMaster Certificate Sync**, make an API request to the [Create Kemp LoadMaster PKI Sync](/api-reference/endpoints/pki/syncs/kemp-loadmaster/create) endpoint.
### Sample request
<Note>
You can optionally specify `certificateIds` during sync creation to immediately add certificates to the sync.
If not provided, you can add certificates later using the certificate management endpoints.
</Note>
```bash Request
curl --request POST \
--url https://app.infisical.com/api/v1/cert-manager/syncs/kemp-loadmaster \
--header 'Authorization: Bearer <access-token>' \
--header 'Content-Type: application/json' \
--data '{
"name": "my-kemp-cert-sync",
"applicationId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"description": "an example certificate sync",
"connectionId": "550e8400-e29b-41d4-a716-446655440000",
"destination": "kemp-loadmaster",
"isAutoSyncEnabled": true,
"certificateIds": [
"550e8400-e29b-41d4-a716-446655440000"
],
"syncOptions": {
"canRemoveCertificates": true,
"preserveItemOnRenewal": true,
"certificateNameSchema": "Infisical-{{certificateId}}"
},
"destinationConfig": {
"virtualServiceId": "1"
}
}'
```
### Sample response
```json Response
{
"pkiSync": {
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"name": "my-kemp-cert-sync",
"description": "an example certificate sync",
"destination": "kemp-loadmaster",
"isAutoSyncEnabled": true,
"destinationConfig": {
"virtualServiceId": "1"
},
"syncOptions": {
"canRemoveCertificates": true,
"preserveItemOnRenewal": true,
"certificateNameSchema": "Infisical-{{certificateId}}"
},
"applicationId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"connectionId": "550e8400-e29b-41d4-a716-446655440000",
"createdAt": "2026-03-31T00:00:00.000Z",
"updatedAt": "2026-03-31T00:00:00.000Z"
}
}
```
</Tab>
The Kemp LoadMaster Certificate Sync provides:
Infisical automatically keeps your LoadMaster certificates in sync:
When a certificate is renewed in Infisical, the behavior depends on the Preserve Certificate on Renewal option:
{{certificateId}}, which would otherwise resolve to a new name on renewal). Ideal for production environments.When certificate removal is enabled and a certificate is no longer active in Infisical:
You can manually trigger certificate synchronization to the LoadMaster using the sync certificates functionality. This is useful for:
To manually sync certificates, use the Sync Certificates API endpoint or the manual sync option in the Infisical UI.