Goal: upload certificates to two different loadmasters from a single source. (internal PKI or Let's Encrypt)
NOTE: I have two different sets of LoadMasters that need the SAME Let's Encrypt certificates - however I am unable to validate the offline VIPS on the secondary set due to it being out of rotation 99% of the time - unless I am missing something obvious I see no other way to keep the certificates good unless I push them to each the Kemp LMs.
Which begs the question - how do I keep my "warm but offline Kemp LE certs up to date"
Firmware version: 7.2.59.1.22028.RELEASE.20230420-1125
following the instruction here ( https://loadmasterapiv2.docs.progress.com/#d8d93823-367c-4286-b3b0-78e7d8e89733) yields a :
{ "code": 400,
"message": "Unknown command",
"status": "fail"
}
the command issued: (both curl and postman fail the same)
curl --location --request GET 'https://myloadmasterurll/accessv2' \
--header 'Content-Type: application/json' \
--data '{
"cmd": "addcert",
"apikey": "S N I P",
"cert": "ExampleCert",
"data": "MIIHDgIBAzCCBsQGCSqGSIb3DQEHAaCCBrUEggaxMIIGrTCCBTIGCSqGSIb3DQEHBqCCBSMwggU" <--SNIP
}'
Raymond Tant
for the record - I base64 encoded a cert and key from a text file into a base64 single line string with the same results.