Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Web Help Desk (WHD) > Web Help Desk (WHD) Documentation > Web Help Desk Administrator Guide > Configure and manage authentication > Add Certificate Chains

Add Certificate Chains

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

Views: 403 Votes: 0 Revisions: 4

A trusted CA can delegate to another CA. In this example, the certificate returned by the delegated CA will be signed by the trusted CA, resulting in a certificate chain. Certificate chains can vary in length. The highest certificate in the chain known as the root certificate should be a self-signed certificate signed by the trusted CA.

Each certificate in the chain must be imported into the keystore so the complete chain can be sent to the Web browser. If the CA Reply does not include the chain certificates, they must be added to the keystore manually before the CA reply.

The certificates must be imported in order of dependency.

To import the certificates:

  1. Add the root certificate first. 
  2. Add the next chained certificate signed by the root certificate.
  3. Add the next chained certificate (and so on) down to the CA reply. 
 
Last modified

Tags

Classifications

Public