Skip to main content
NetApp Knowledge Base

Adding a cluster to AIQUM 9.16P2 fails when SAML is enabled

Views:
178
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

Applies to

  • Active IQ Unified Manager (AIQUM) 9.16+
  • ONTAP cluster with SAML enabled

Issue

  • Adding a cluster to AIQUM using a local admin account fails with an exception if SAML is enabled on the cluster.

  • Error seen in ocumserver.log:
2025-07-24 17:14:57,970 ERROR [bandit] [default task-8] [c.n.d.c.l.s.cert.CertGenerator] Error fetching timezone for the cluster
2025-07-24 17:14:57,973 ERROR [bandit] [default task-8] [c.n.d.o.o.OntapMutualAuthenticationManager] Exception installing Mutual TLS certificate on ONTAP
org.bouncycastle.operator.OperatorCreationException: Error fetching the cluster timezone for certificate creation
    at deployment.dfm-app.war//com.netapp.dfm.common.lite.security.cert.CertGenerator.generateSelfSignedCertificate(CertGenerator.java:414)
    at deployment.dfm-app.war//com.netapp.dfm.ontap.outbound.OntapMutualAuthenticationManager.generateCertificate(OntapMutualAuthenticationManager.java:201)
    at deployment.dfm-app.war//com.netapp.dfm.ontap.outbound.OntapMutualAuthenticationManager.enableMutualAuthentication(OntapMutualAuthenticationManager.java:82)

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.