Submit a ticketCall us

Announcing NPM 12.2
With NPM 12.2 you can monitor your Cisco ASA firewalls, to monitor VPN tunnels for basic visibility and troubleshooting tunnels. NPM 12.2 also uses the SolarWinds Orion Installer so you can easily install and upgrade one or more Orion Platform products simultaneously.
See new features and improvements.

Home > Success Center > Web Help Desk (WHD) > Web Help Desk Administrator Guide > Configure and manage authentication > Import a PKCS#12 File into the Keystore

Import a PKCS#12 File into the Keystore

Table of contents
No headers
Created by Steve.Hawkins, last modified by Anthony.Rinaldi_ret on Jul 19, 2016

Views: 43 Votes: 0 Revisions: 4

Portecle provides two ways to import the contents of a PKCS#12 file into the Web Help Desk Java keystore.

  • Open the PKCS#12 keystore in File > Open Keystore File, convert it to a Java keystore in Tools > Change Keystore Type > JKS, and overwrite the existing keystore by saving it as WebHelpDesk/conf/keystore.jks.
  • Open the Web Help Desk keystore file and import the keypair containing your certificate using Tools > Import Keypair. Portecle prompts you to select which keypair in your PKCS#12 keystore to import.

If your keystore contains a default, unsigned Tomcat certificate, delete this certificate before you import your PKCS#12 file.

When you import your file, ensure that:

  • Your certificate chain is intact in the Web Help Desk keystore. You can inspect the certificate chain by double-clicking the certificate to view the certificate details. Use the left and right arrows at the top of the details panel to navigate through each certificate in the chain. If you do not see the full certificate chain, try importing the CA certificates first at Tools > Import Trusted Certificate and then import your keypair again. Portecle does not establish trust when a certificate is imported before the certificate that was used to sign it.
  • Your root certificate is imported first, then the next certificate in the chain, and so on until you get to your own certificate.
  • Your certificate is aliased as tomcat. The password for your certificate and the keystore must be identical and match the KEYSTORE_PASSWORD setting in the WebHelpDesk/conf/whd.conf file (changeit by default).
Last modified
07:53, 19 Jul 2016