Skip to main content
NetApp Knowledge Base

What are the API methods for setting custom SSL certificates on the Element mNode?

Views:
671
Visibility:
Public
Votes:
0
Category:
element-software
Specialty:
solidfire
Last Updated:

Applies to

  • Element Software versions 11.3 and above
  • Element Management Node (mNode) versions 11.3 and above

Answer

As of versions 11.3 and above, the following API methods can be used to view, change, or reset the SSL certificate in place on the mNode:

The text of the certificate itself will be submitted in the payload of the https POST request, in the 'privateKey' and 'certificate' parameters. There are various ways to do this, such as:

Warnings: 

  • after changing the SSL certificate on the Element cluster itself or the management node, the management node then needs to be rebooted in order to sync up  authentication between the mNode and the cluster (the cluster storage nodes do not need to be rebooted)
  • if the Configure Fully Qualified Domain Name web UI access has previously been applied in order to reach the cluster via FQDN, the steps therein may need to be re-applied after changing the cluster SSL certificate (check cluster access via FQDN, re-apply steps if needed)

 

Additional Information

The above API's are for the mNode specifically; to manage the SSL certificate on the Element cluster itself (and all storage nodes therein), the equivalent API's are:

 

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.