Tools
Apply an SSL certificate to Web Help Desk in Linux via command line interface
This procedure applies to the SolarWinds WebHelpDesk VA (Virtual Appliance).
First published date
Last published date
Overview
This procedure applies to the SolarWinds WebHelpDesk VA (Virtual Appliance). To apply an SSL Certificate to WHD in Linux via CLI, complete the steps below.
Product section
Resolution
- SSH to the machine as a user with sudo access.
- Change the directory to the WHD home folder:
cd /usr/local/webhelpdesk/conf
- Edit the file /usr/local/webhelpdesk/conf/whd.conf and uncomment the line for HTTPS_PORT=443.
- Look for KEYSTORE_PASSWORD= and take note of the password.
- Delete the alias tomcat from the keystore. You may also backup the keystore before doing this:
sudo ../bin/jre/bin/keytool -delete -alias tomcat -keystore keystore.jks -storepass [the password from step 3]
- Generate a new key with alias tomcat:
SHA1 Signature Algorithm: sudo ../bin/jre/bin/keytool -genkey -alias tomcat -keystore keystore.jks -keyalg RSA -keysize 2048 -validity <val_days> -storepass [the password from step 3] SHA2 Signature Algorithm: sudo ../bin/jre/bin/keytool -genkey -alias tomcat -keystore keystore.jks -keyalg RSA -sigalg SHA256withRSA -keysize 2048 -validity <val_days> -storepass [the password from step 3]
<val_days>= days that the key is valid, 365 for 1 year and 730 for 2 years.then- Enter a CN that matches the site used in the certificate For example, if Web Help Desk is hosted at support.example.com, your CN must be support.example.com.
- Enter an Organization Unit (OU) that helps distinguish this certificate from others for your organization.
- Enter an Organization Name (O), typically name for your organization.
- Locality Name (L). This is typically a city name.
- Enter a State Name (ST). This should be the unabbreviated city and state/province/region/territory of your organization.
- Enter a Country (C) This should be the two letter ISO 3166 country code for your country.
- Email (E) is generally optional, but may be used by your CA as the address to which the certificate will be mailed.
- Generate a CSR file or Certificate Signing Request file:
sudo ../bin/jre/bin/keytool -certreq -alias tomcat -keystore keystore.jks -file <[filename].csr> -storepass [the password from step 3]
- Grab a copy of that .csr file and send it to your root CA to request for a signed certificate.
- Once you have already downloaded the signed certificate and root certificates, you can then import them as follows:
- Copy the files to the VA using an SFTP client (like FileZilla or WinSCP) and take note of the location.
- Import the Root and intermediate CA certificates (repeat the same step below for every certificate and change the alias to a different name):
sudo ../bin/jre/bin/keytool -import -trustcacerts -alias root -file </path/to/Root CA file> -keystore keystore.jks -storepass [the password from step 3]
- Import the singed primary CA for WHD (tomcat):
sudo ../bin/jre/bin/keytool -import -trustcacerts -alias tomcat -file </path/to/your.whd.authenticated cert> -keystore keystore.jks -storepass [the password from step 3]
- You may also refer to this topic in the WHD Administrator Guide but this will require a separate download of the OpenSource tool - Portecle .
- Verify the keystore file by running the following command:
sudo ../bin/jre/bin/keytool -v -list -keystore keystore.jks -storepass [the password from step 3]
Disclaimer: Please note, any content provided herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.