Skip to main content
NetApp Knowledge Base

ONTAP S3/Trident Server CA Certificate Renewal Fails to Add SAN

  1. Last updated
  2. Save as PDF
Views:
26
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9.13.1P7 and later
  • S3 Object Store Server 
  • Kubernetes image registry using ONTAP S3 backend

Issue

After renewing the S3/Trident server CA certificate on ONTAP, the OpenShift image registry is unavailable due to certificate validation errors. 
The OpenShift platform requires the certificate to include a Subject Alternative Name (SAN) field, but the renewed certificate is missing this extension.

# cat s3_prod_cert.txt | awk '/-----BEGIN CERTIFICATE-----/,/-----END CERTIFICATE-----/' | openssl x509 -noout -issuer -subject -ext subjectAltName
issuer=CN=s3-prod.112.up.gov.in,C=US
subject=CN=s3-prod.112.up.gov.in,C=US
No extensions in certificate
# cat s3_prod_cert.txt | awk '/-----BEGIN CERTIFICATE-----/,/-----END CERTIFICATE-----/' | certexplorer -f issuer,subject,san
Issuer: CN=s3-prod.112.up.gov.in,C=US
Subject: CN=s3-prod.112.up.gov.in,C=US
SubjectAlternativeName:
OpenShift registry pod log:
tls: failed to verify certificate: x509: certificate relies on legacy CommonName field, use SANs instead

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.