
RootCA.example.internal
Root Certificate Authority: RootCA
| RootCA’s Info + | 
| RootCA’s | 
| Public Key | 
| RootCA’s Digital | 
| Signature | 
RootCA’s Certificate
| R2’s Info + | 
| R2’s Public Key | 
| RootCA’s Digital | 
| Signature | 
R2’s Certificate
R2.example.internal
Subordinate Certificate Authority: R2
What Certificates should be configured on
Jetdirect so that an SSL Client will be
successful?
RootCA’s Info +
CORRECT!
RootCA’s
Public Key
RootCA’s Digital
Signature
RootCA’s Certificate
| LJ 4345MFP’s Info + | 
| Public Key | 
| R2’s Digital | 
| Signature | 
LJ 4345MFP’s Identity
Certificate
Figure 35 - Correct HP Jetdirect CA Configuration
Be sure the Root CA of your CA Hierarchy has its public key certificate configured on Jetdirect!
Here is a question for you: When Jetdirect is acting as a client and receives the server’s certificate
signed by R2, how can it know that R2’s certificate was signed by RootCA? The answer: It cannot!
Another special thing must happen: The server must send R2’s CA certificate along with its own certificate. This allows Jetdirect to “walk the chain” and verify the certificate chain is valid. Refer to Figure 36 – Walking the Chain 1
81