Tools

Add a Subject Alternative Name (SAN) to an existing certificate

This article describes how to add a Subject Alternative Name (SAN) to an existing WHD-signed SSL certificate.

First published date

10/18/2018 2:30 PM

Last published date

9/10/2020 3:16 PM

Overview

This is how you add a Subject Alternative Name in the Web Help Desk SSL Certificate.  Due to an update in Google Chrome only the subjectAlternativeName (SAN) extension, not commonName(CN), is used to match the domain name and site certificate.

Product section

Web Help Desk

Resolution

  1. Log in to the WHD server.
  2. Go to whd_install_dir/conf and create a backup of the keystore.jks file.
  3. Open a command prompt window.
  4. Go to the WebHelpDesk folder.
    • Microsoft Windows: C:\Program Files\WebHelpDesk\
    • Linux or Virtual Appliance: /usr/local/webhelpdesk/
    • Mac OS X: /Library/WebHelpDesk/
  5. Enter the following command:
    /bin/jre/bin/keytool -genkey -keystore WHD_INSTALL_DIR/conf/keystore.jks -alias tomcat -ext SAN=dns:DOMAIN_NAME -keyalg RSA -dname "CN=DOMAIN_NAME, OU=Organizational unit, O=Organization, L=City or locality, ST=State or province, C=Two-letter country code" -keypass KEYSTORE_PASSWORD -storepass KEYSTORE_PASSWORD -validity daysvalid -sigalg SHA256withRSA
  6.  

     as an example for Windows with the following:

    DOMAIN_NAME=domain.com

    SAN=webhelpdesk.domain.com

    CN=wehelpdesk.domain.com

    OU=IT

    O= IT Services

    L=Tampa

    ST=Florida

    C=US

    KEYSTORE_PASSWORD=changeit

    daysvalid=365

     

    "C:\Program Files\WebHelpDesk\bin\jre\bin\keytool" -genkey -keystore "C:\Program Files\WebHelpDesk\conf\keystore.jks" -alias tomcat -ext SAN=dns:webhelpdesk.domain.com -keyalg RSA -dname "CN=webhelpdesk.domain.com, OU=IT, O=Tampa Org, L=Tampa, ST=Florida, C=US" -keypass changeit -storepass changeit -validity 365 -sigalg SHA256withRSA 

     

     

  7. Stop and start the WHD service.

Disclaimer: Please note, any content posted 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.