<?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 Re: Splunkweb Certificate issue in Security</title>
    <link>https://community.splunk.com/t5/Security/Splunkweb-Certificate-issue/m-p/390091#M9518</link>
    <description>&lt;P&gt;Hello @rohitvjoshi &lt;/P&gt;

&lt;P&gt;The best approach to create cert in Splunk is mentioned below :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;    1. Go to $SPLUNK_HOME\etc\auth\splunkweb
    2. Rename cert.pem to cert.pem_backup
    3. Restart the splunk using command ./splunk restart
    4. After restart you will be able to see a new cert.pem file.
    5. Check the expiry date of Certificate now using command: $SPLUNK_HOME\bin\openssl x509 -enddate -noout -in $SPLUNK_HOME/etc/auth/splunkweb/cert.pem
    6. The expiry date will be extended.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Do this one by one for all the SH servers if you want to update it for all the SH, but it is not required till the time they are coming near expiry date. &lt;/P&gt;</description>
    <pubDate>Mon, 18 Feb 2019 06:59:21 GMT</pubDate>
    <dc:creator>vishaltaneja070</dc:creator>
    <dc:date>2019-02-18T06:59:21Z</dc:date>
    <item>
      <title>Splunkweb Certificate issue</title>
      <link>https://community.splunk.com/t5/Security/Splunkweb-Certificate-issue/m-p/390090#M9517</link>
      <description>&lt;P&gt;Hi Splunkers, &lt;/P&gt;

&lt;P&gt;we are using clustered enviornment, we having 3 SH .We have notified by infra team that one of our searchheads certficate is expiring on this month. this is cert.pem under $splunk_home/etc/auth/splunkweb.We have to create the Splunkweb selefsigned certificate for the same. we will follow the below steps provided in doc:&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.2.4/Security/SecureSplunkWebusingasignedcertificate"&gt;https://docs.splunk.com/Documentation/Splunk/7.2.4/Security/SecureSplunkWebusingasignedcertificate&lt;/A&gt;&lt;BR /&gt;
we also have to change the web.conf file , as per below document it says in case of deployment manger we have to change the path of certificate over there:&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.2.4/Security/SecureSplunkWebusingasignedcertificate"&gt;https://docs.splunk.com/Documentation/Splunk/7.2.4/Security/SecureSplunkWebusingasignedcertificate&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;My Question is :&lt;BR /&gt;
1:As we are changing the web.conf file in deployer , it will applicable for all 3 SH, so we have to create self-signed certs in all 3 SH ?&lt;BR /&gt;
1. what is our approach for Splunkweb certs in case of Clustered enviornmant . &lt;/P&gt;

&lt;P&gt;please help !!&lt;/P&gt;

&lt;P&gt;Thanks &lt;/P&gt;</description>
      <pubDate>Sat, 16 Feb 2019 14:25:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunkweb-Certificate-issue/m-p/390090#M9517</guid>
      <dc:creator>rohitvjoshi</dc:creator>
      <dc:date>2019-02-16T14:25:25Z</dc:date>
    </item>
    <item>
      <title>Re: Splunkweb Certificate issue</title>
      <link>https://community.splunk.com/t5/Security/Splunkweb-Certificate-issue/m-p/390091#M9518</link>
      <description>&lt;P&gt;Hello @rohitvjoshi &lt;/P&gt;

&lt;P&gt;The best approach to create cert in Splunk is mentioned below :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;    1. Go to $SPLUNK_HOME\etc\auth\splunkweb
    2. Rename cert.pem to cert.pem_backup
    3. Restart the splunk using command ./splunk restart
    4. After restart you will be able to see a new cert.pem file.
    5. Check the expiry date of Certificate now using command: $SPLUNK_HOME\bin\openssl x509 -enddate -noout -in $SPLUNK_HOME/etc/auth/splunkweb/cert.pem
    6. The expiry date will be extended.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Do this one by one for all the SH servers if you want to update it for all the SH, but it is not required till the time they are coming near expiry date. &lt;/P&gt;</description>
      <pubDate>Mon, 18 Feb 2019 06:59:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunkweb-Certificate-issue/m-p/390091#M9518</guid>
      <dc:creator>vishaltaneja070</dc:creator>
      <dc:date>2019-02-18T06:59:21Z</dc:date>
    </item>
    <item>
      <title>Re: Splunkweb Certificate issue</title>
      <link>https://community.splunk.com/t5/Security/Splunkweb-Certificate-issue/m-p/390092#M9519</link>
      <description>&lt;P&gt;Thanks for your answer, this approach is worked for cert.pem but to renew the certificates in under splunkweb , we have to create the self-signed certificates(SplunkWebPrivateKey &amp;amp;  SplunkWebCertificate.pem) and change the certificate path in web.conf.&lt;BR /&gt;
Configure Splunk Web to use the key and certificate files:&lt;BR /&gt;
-In $SPLUNK_HOME/etc/system/local/web.conf, make the following changes to the [settings] stanza:&lt;BR /&gt;
[settings]&lt;BR /&gt;
enableSplunkWebSSL = true&lt;BR /&gt;
privKeyPath =&lt;BR /&gt;&lt;BR /&gt;
serverCert =  &lt;/P&gt;

&lt;P&gt;Thanks &lt;BR /&gt;
Rohit Joshi &lt;/P&gt;</description>
      <pubDate>Wed, 24 Apr 2019 07:52:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunkweb-Certificate-issue/m-p/390092#M9519</guid>
      <dc:creator>rohitvjoshi</dc:creator>
      <dc:date>2019-04-24T07:52:15Z</dc:date>
    </item>
  </channel>
</rss>

