<?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 unable to update SSL certificate -Cannot decrypt private key -Splunk 9.0.0 in Security</title>
    <link>https://community.splunk.com/t5/Security/unable-to-update-SSL-certificate-Cannot-decrypt-private-key/m-p/678928#M17644</link>
    <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;We're in the process of updating the SSL certificates on our Splunk servers. However, when attempting the upgrade, we encounter the following error:&lt;/P&gt;&lt;P&gt;"Cannot decrypt private key in "/opt/splunk/etc/apps/*/local/Splunk.key" without a password. Network communication with splunkweb may fail or hang. Consider using an unencrypted private key for Splunkweb's SSL certificate."&lt;/P&gt;&lt;P&gt;Could anyone provide assistance with this issue?&lt;/P&gt;&lt;P&gt;Below are the steps we followed while generating the certificate. Please let us know if you spot any mistakes. We're running Splunk 9.0.0.&lt;/P&gt;&lt;P&gt;## Go to /root/certs/&lt;BR /&gt;cd /root/certs/&lt;/P&gt;&lt;P&gt;## Create new directory for the certs&lt;BR /&gt;mdkir certs_2024&lt;/P&gt;&lt;P&gt;## Create Server Key&lt;BR /&gt;openssl genrsa -des3 -out splunk.key 2048&lt;BR /&gt;password123######&lt;BR /&gt;password123######&lt;BR /&gt;&lt;BR /&gt;## Create a No Pass Key&lt;BR /&gt;openssl rsa -in splunk.key -out splunk.nopass.key&lt;BR /&gt;enter passphrase - &amp;lt;&amp;lt;&amp;lt;password&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;&lt;BR /&gt;## Generate the csr file&lt;BR /&gt;openssl req -new -sha256 -key splunk.nopass.key -out splunk.csr&lt;/P&gt;&lt;P&gt;&amp;nbsp;once we get the certificate, we are running the below steps.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;vi end_entity_cert &amp;lt;&amp;lt;paste the end_entity_cert value for the hostname and save&amp;gt;&amp;gt;&lt;/P&gt;&lt;P&gt;vi intermediate_cert &amp;lt;&amp;lt;paste the intermediate_cert value for the hostname and save&amp;gt;&amp;gt;&lt;BR /&gt;cp splunk.nopass.key /opt/splunk/etc/apps/App_hostname_ssl/local&lt;/P&gt;&lt;P&gt;Go to certificates folder - cd /home/Splunk/certs_renewal/&lt;/P&gt;&lt;P&gt;Copy the rootCA.pem into /opt/splunk/etc/apps/App_hostname_ssl/local&lt;/P&gt;&lt;P&gt;## Create Certificate Chain&lt;/P&gt;&lt;P&gt;cat end_entity_cert splunk.key intermediate_cert rootCA.pem &amp;gt;&amp;gt;full.pem&lt;BR /&gt;&lt;BR /&gt;## Verify Certificate Validity&lt;/P&gt;&lt;P&gt;openssl x509 -enddate -noout -in full.pem&lt;/P&gt;&lt;P&gt;./splunk restart&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 28 Feb 2024 07:19:57 GMT</pubDate>
    <dc:creator>saibargavg</dc:creator>
    <dc:date>2024-02-28T07:19:57Z</dc:date>
    <item>
      <title>unable to update SSL certificate -Cannot decrypt private key -Splunk 9.0.0</title>
      <link>https://community.splunk.com/t5/Security/unable-to-update-SSL-certificate-Cannot-decrypt-private-key/m-p/678928#M17644</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;We're in the process of updating the SSL certificates on our Splunk servers. However, when attempting the upgrade, we encounter the following error:&lt;/P&gt;&lt;P&gt;"Cannot decrypt private key in "/opt/splunk/etc/apps/*/local/Splunk.key" without a password. Network communication with splunkweb may fail or hang. Consider using an unencrypted private key for Splunkweb's SSL certificate."&lt;/P&gt;&lt;P&gt;Could anyone provide assistance with this issue?&lt;/P&gt;&lt;P&gt;Below are the steps we followed while generating the certificate. Please let us know if you spot any mistakes. We're running Splunk 9.0.0.&lt;/P&gt;&lt;P&gt;## Go to /root/certs/&lt;BR /&gt;cd /root/certs/&lt;/P&gt;&lt;P&gt;## Create new directory for the certs&lt;BR /&gt;mdkir certs_2024&lt;/P&gt;&lt;P&gt;## Create Server Key&lt;BR /&gt;openssl genrsa -des3 -out splunk.key 2048&lt;BR /&gt;password123######&lt;BR /&gt;password123######&lt;BR /&gt;&lt;BR /&gt;## Create a No Pass Key&lt;BR /&gt;openssl rsa -in splunk.key -out splunk.nopass.key&lt;BR /&gt;enter passphrase - &amp;lt;&amp;lt;&amp;lt;password&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;&lt;BR /&gt;## Generate the csr file&lt;BR /&gt;openssl req -new -sha256 -key splunk.nopass.key -out splunk.csr&lt;/P&gt;&lt;P&gt;&amp;nbsp;once we get the certificate, we are running the below steps.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;vi end_entity_cert &amp;lt;&amp;lt;paste the end_entity_cert value for the hostname and save&amp;gt;&amp;gt;&lt;/P&gt;&lt;P&gt;vi intermediate_cert &amp;lt;&amp;lt;paste the intermediate_cert value for the hostname and save&amp;gt;&amp;gt;&lt;BR /&gt;cp splunk.nopass.key /opt/splunk/etc/apps/App_hostname_ssl/local&lt;/P&gt;&lt;P&gt;Go to certificates folder - cd /home/Splunk/certs_renewal/&lt;/P&gt;&lt;P&gt;Copy the rootCA.pem into /opt/splunk/etc/apps/App_hostname_ssl/local&lt;/P&gt;&lt;P&gt;## Create Certificate Chain&lt;/P&gt;&lt;P&gt;cat end_entity_cert splunk.key intermediate_cert rootCA.pem &amp;gt;&amp;gt;full.pem&lt;BR /&gt;&lt;BR /&gt;## Verify Certificate Validity&lt;/P&gt;&lt;P&gt;openssl x509 -enddate -noout -in full.pem&lt;/P&gt;&lt;P&gt;./splunk restart&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Feb 2024 07:19:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/unable-to-update-SSL-certificate-Cannot-decrypt-private-key/m-p/678928#M17644</guid>
      <dc:creator>saibargavg</dc:creator>
      <dc:date>2024-02-28T07:19:57Z</dc:date>
    </item>
    <item>
      <title>Re: unable to update SSL certificate -Cannot decrypt private key -Splunk 9.0.0</title>
      <link>https://community.splunk.com/t5/Security/unable-to-update-SSL-certificate-Cannot-decrypt-private-key/m-p/678952#M17647</link>
      <description>&lt;P&gt;It's not all that's at play here but you're creating a whole lot of files (you could just create a key with -nodes option to have it non-encrypted) and your config apparently points to splunk.key which - judging by the sequence of commands - is encrypted.&lt;/P&gt;&lt;P&gt;As a side note - putting your private key into an app is not necessarily the most secure thing to do.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Feb 2024 11:46:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/unable-to-update-SSL-certificate-Cannot-decrypt-private-key/m-p/678952#M17647</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-02-28T11:46:22Z</dc:date>
    </item>
  </channel>
</rss>

