Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Web Help Desk (WHD) > 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: 32 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, add the root certificate first, and then the next chained certificate signed by the root certificate (and so on) down to the CA reply.

 
Last modified
15:50, 18 Jul 2016

Tags

Classifications

Public