Quantcast
Channel: Ivanti User Community : All Content - Cloud Services Appliance
Viewing all articles
Browse latest Browse all 418

How to Add a Third Party Certificate to a Cloud Service Appliance version 4.2 and newer

$
0
0

If 2048 SSL certificate is required on a Cloud Service Appliance, you will need to purchase such certificate from a third party. See SSL Certificate Requirements here: SSL Certificate Requirements for LANDESK Cloud Service Appliance.


On the Cloud Services Appliance go to Manage LDMG certificates.


LDMGcerts.png




Click Create CSR. Enter info and click Display to get CSR.


LDMGCertsCreateCSR.png

Fill out the signing request with your information, see example below:

LDMGCSR.png


*Note - SSL certificate must be purchased in SHA-1. Some vendors may be phasing out SHA-1 by January 1st, 2017, so purchasing more than 2 years may not give the option for SHA-1.


LDMGDisplay.png

LDMGCopy.png

 

LDMGRequestCert.png

 

LDMGCertAdd.png

 

 

 

Download SSL cert info from vendor. Copy the certificate info. Open a web console to the CSA, go to Manage LDMS certificates, click Add LDMG certificate and paste the SSL text/response document into the box. Click save.


LDMGcert.png



Remove the self-signed default SSL certs in LDMG Certificates and reboot the Cloud Service Appliance. Log back into the CSA. Under LDMG certificates, you should see 3 certs, the request, the end entity and the self-signed one.

 

Note: If you put in a SHA-2 or SHA-256 you will not be able to log back into the gateway. It is not supported. To fix this, go onto the gateway itself, press Alt+F1 which will open a console window.

 

  1. Type sudo su
  2. Type the admin password
  3. cd /root/.certs
  4. Delete the 2 certificates with the rm command.
  5. Reboot, and you should be able to login to the CSA again.
  6. Make sure to only use SHA-1 certificate so this doesn't happen.



Viewing all articles
Browse latest Browse all 418

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>