Skip to main content
NetApp Knowledge Base

What are common reasons that a signed CA certificate is still not trusted?

  1. Last updated
    Jul 6, 2022
  2. Save as PDF
Views:
605
Visibility:
Public
Votes:
0
Category:
ontap-system-manager
Specialty:
om
Last Updated:
7/6/2022, 4:41:32 PM

Applies to

ONTAP System Manager 9

Answer

  1. The certificate is not issued by a commonly trusted Certificate Authority (CA) but internally. You need to push the root and intermediate(if applicable) certificate(s) to all clients which shall have trusted connections.
  2. The certicate CA sign request was created with a different private key. You need to repeate the certificate creating, signig request, signing and certificate import.
  3. SSL installation was not completed properly or the private key was lost.  You need to repeate the certificate creating, signig request, signing and certificate import.
  4. The Certificate is expired. You need to create a new certificate, signig request, sign it and import the signed certificate.

Additional Information

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.