Try following the procedure listed here, http://support.citrix.com/article/CTX133468

Thanks for info Somesh.

I came across that guide before and tried to upload my SSL cert through the API.  However, I kept getting the error

"Unable to execute API command uploadcustomcertificate due to missing parameter certificate"

My API call looks like this:

curl http://localhost:8096/client/api?command=uploadCustomCertificate&id=1&name=root1&domainsuffix=mydomain.com&certificate=-----BEGIN%20CERTIFICATE%20REQUEST-----<rootcertificate>-----END%20CERTIFICATE%20REQUEST-----

The command looks exactly like the guide but it keeps giving the missing parameter error.

Thanks. 

Edited by Ravi Bandara, 06 February 2015 - 08:19 PM.

Can you make sure you are uploading the correct root certificate? The reason I ask is I see text like "certificate request".

That's one thing I've never been able to find a clear answer on.

I have the following:

- private key

- csr generated from private key

- certificate from RapidSSL generated using csr

- primary and secondary intermediate CA from RapidSSL

- PKCS#8 Private Key

Which one am I supposed to be using?  I've tried URL encoded versions of all of them, except the intermediate keys, in the API call but keep getting the missing parameter error.

Edited by Ravi Bandara, 06 February 2015 - 09:21 PM.

You need CA's root certificate. Check with RapidSSL, they should help you in getting the root and intermediate certificates.

Thanks, I will contact RapidSSL and proceed from there.

I got in contact with RapidSSL and provided the link to download their CA root certificated.

https://knowledge.rapidssl.com/support/ssl-certificate-support/index?page=content&id=SO8834&actp=AGENT_REFERAL

I was able to fix my original issue by uploading the certs again using the UI.  Now the browsers I've tested with (Chrome, IE, Firefox) no longer see realhostip.com.

However, with the correct CA root cert, I was still not able to upload it via the API.

I still keep getting the missing parameter error.

This is why my API call looks like in full (with the domain edited out)

curl http://localhost:8096/client/api?command=uploadCustomCertificate&id=1&name=root1&domainsuffix=mydomain.com&certificate=-----BEGIN%20CERTIFICATE-----%0AMIIDVDCCAjygAwIBAgIDAjRWMA0GCSqGSIb3DQEBBQUAMEIxCzAJBgNVBAYTAlVT%0AMRYwFAYDVQQKEw1HZW9UcnVzdCBJbmMuMRswGQYDVQQDExJHZW9UcnVzdCBHbG9i%0AYWwgQ0EwHhcNMDIwNTIxMDQwMDAwWhcNMjIwNTIxMDQwMDAwWjBCMQswCQYDVQQG%0AEwJVUzEWMBQGA1UEChMNR2VvVHJ1c3QgSW5jLjEbMBkGA1UEAxMSR2VvVHJ1c3Qg%0AR2xvYmFsIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2swYYzD9%0A9BcjGlZ%2BW988bDjkcbd4kdS8odhM%2BKhDtgPpTSEHCIjaWC9mOSm9BXiLnTjoBbdq%0AfnGk5sRgprDvgOSJKA%2BeJdbtg%2FOtppHHmMlCGDUUna2YRpIuT8rxh0PBFpVXLVDv%0AiS2Aelet8u5fa9IAjbkU%2BBQVNdnARqN7csiRv8lVK83Qlz6cJmTM386DGXHKTubU%0A1XupGc1V3sjs0l44U%2BVcT4wt%2FlAjNvxm5suOpDkZALeVAjmRCw7%2BOC7RHQWa9k0%2B%0Abw8HHa8sHo9gOeL6NlMTOdReJivbPagUvTLrGAMoUgRx5aszPeE4uwc2hGKceeoW%0AMPRfwCvocWvk%2BQIDAQABo1MwUTAPBgNVHRMBAf8EBTADAQH%2FMB0GA1UdDgQWBBTA%0AephojYn7qwVkDBF9qn1luMrMTjAfBgNVHSMEGDAWgBTAephojYn7qwVkDBF9qn1l%0AuMrMTjANBgkqhkiG9w0BAQUFAAOCAQEANeMpauUvXVSOKVCUn5kaFOSPeCpilKIn%0AZ57QzxpeR%2BnBsqTP3UEaBU6bS%2B5Kb1VSsyShNwrrZHYqLizz%2FTt1kL%2F6cdjHPTfS%0AtQWVYrmm3ok9Nns4d0iXrKYgjy6myQzCsplFAMfOEVEiIuCl6rYVSAlk6l5PdPcF%0APseKUgzbFbS9bZvlxrFUaKnjaZC2mqUPuLk%2FIH2uSrW4nOQdtqvmlKXBx4Ot2%2FUn%0Ahw4EbNX%2F3aBd7YdStysVAq45pmp06drE57xNNB6pXE0zX5IJL4hmXXeXxx12E6nV%0A5fEWCRE11azbJHFwLJhWC9kXtNHjUStedejV0NxPNO3CBWaAocvmMw%3D%3D%0A-----END%20CERTIFICATE-----

I was using an online tool for URL encoding (http://meyerweb.com/eric/tools/dencoder/) but it looked to be encoding correctly.

Thanks for the point in the right direction.  My original issue is resolved but was never able to upload via API.