<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic PowerShell script to replace the  Self-Signed Certificate on multiple SVMs in Software Development Kit (SDK) and API Discussions</title>
    <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/PowerShell-script-to-replace-the-Self-Signed-Certificate-on-multiple-SVMs/m-p/145270#M2789</link>
    <description>&lt;P&gt;I was working on vulnerabilities remediation, and we had to fix&amp;nbsp;a “SSL Certificate Self-Signed” vulnerability related to Storage Virtual Machines (SVMs/vservers). Since we have many SVMs, I decided to automate the process as the manual process is cumbersome and time-consuming. The script assumes you have only one issued wildcard certificate to apply to all SVMs. In the future, I will work on a second version of the script so each SVM can have its own certificate. The script workflow is as follows:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; 1) Creates a folder for each SVM as it progresses.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; 2) Copies the existing SSL/Cert of the SVM into a file and saves it into the SVM folder.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; 3) Deletes the existing/default cert. If successful, it will create an empty file (Deleting_SSLcert_was_successful.txt) in that SVM folder. This is just for confirmation.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; 4) Applies the issued certificate and copies the newly applied SSL/Cert information of the SVM into a new file and saves it in the same SVM folder.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; 5) Modifies the SVM to use the new SSL/Cert settings.&lt;/P&gt;</description>
    <pubDate>Thu, 06 Dec 2018 20:40:32 GMT</pubDate>
    <dc:creator>RB00000</dc:creator>
    <dc:date>2018-12-06T20:40:32Z</dc:date>
    <item>
      <title>PowerShell script to replace the  Self-Signed Certificate on multiple SVMs</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/PowerShell-script-to-replace-the-Self-Signed-Certificate-on-multiple-SVMs/m-p/145270#M2789</link>
      <description>&lt;P&gt;I was working on vulnerabilities remediation, and we had to fix&amp;nbsp;a “SSL Certificate Self-Signed” vulnerability related to Storage Virtual Machines (SVMs/vservers). Since we have many SVMs, I decided to automate the process as the manual process is cumbersome and time-consuming. The script assumes you have only one issued wildcard certificate to apply to all SVMs. In the future, I will work on a second version of the script so each SVM can have its own certificate. The script workflow is as follows:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; 1) Creates a folder for each SVM as it progresses.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; 2) Copies the existing SSL/Cert of the SVM into a file and saves it into the SVM folder.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; 3) Deletes the existing/default cert. If successful, it will create an empty file (Deleting_SSLcert_was_successful.txt) in that SVM folder. This is just for confirmation.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; 4) Applies the issued certificate and copies the newly applied SSL/Cert information of the SVM into a new file and saves it in the same SVM folder.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; 5) Modifies the SVM to use the new SSL/Cert settings.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Dec 2018 20:40:32 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/PowerShell-script-to-replace-the-Self-Signed-Certificate-on-multiple-SVMs/m-p/145270#M2789</guid>
      <dc:creator>RB00000</dc:creator>
      <dc:date>2018-12-06T20:40:32Z</dc:date>
    </item>
  </channel>
</rss>

