<?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: two SSL Certificates on a single indexer / forwarder in Security</title>
    <link>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362399#M9078</link>
    <description>&lt;P&gt;will be completing this in a day or two.. will update soon.&lt;/P&gt;</description>
    <pubDate>Wed, 28 Jun 2017 04:30:39 GMT</pubDate>
    <dc:creator>inventsekar</dc:creator>
    <dc:date>2017-06-28T04:30:39Z</dc:date>
    <item>
      <title>two SSL Certificates on a single indexer / forwarder</title>
      <link>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362395#M9074</link>
      <description>&lt;P&gt;Hi All, &lt;BR /&gt;
1. can we deploy two SSL certificates (self signed) on a single indexer(either same port/different port)&lt;BR /&gt;
2. for Certificates renewal, I have been thinking this process - can one UF be deployed with two SSL Certificates?&lt;BR /&gt;
please suggest regarding this below process.. any improvements/suggestions please. &lt;/P&gt;

&lt;P&gt;===================================================================&lt;BR /&gt;
Normal situation (SSL deployed)&lt;/P&gt;

&lt;P&gt;Indexer1(IP - 10.11.12.13)        -------                    Indexer2  (IP-10.11.12.14)&lt;BR /&gt;
Inputs.conf (SSL-Cert-1)           --------                    inputs.conf (SSL- Cert 1)&lt;/P&gt;

&lt;P&gt;UF1                                                          UF2&lt;BR /&gt;
outputs.conf file &lt;BR /&gt;
[tcpout:splunkssl]&lt;BR /&gt;
server = 10.11.12.13:9997, 10.11.12.14:9997&lt;BR /&gt;
compressed = true&lt;BR /&gt;
sslVerifyServerCert = false&lt;BR /&gt;
sslRootCAPath = $SPLUNK_HOME/etc/auth/cacert.pem&lt;BR /&gt;
sslCertPath = $SPLUNK_HOME/etc/auth/server.pem&lt;BR /&gt;
sslPassword = password&lt;/P&gt;

&lt;P&gt;===================================================================&lt;BR /&gt;
During Certificate renewal - &lt;/P&gt;

&lt;P&gt;Indexer1(IP - 10.11.12.13)       ------------------                     Indexer2  (IP-10.11.12.14)&lt;BR /&gt;
Inputs.conf (SSL-Cert-1)           ---------------------                    inputs.conf (SSL- Cert 2)&lt;/P&gt;

&lt;P&gt;UF1                                                                        UF2&lt;BR /&gt;
outputs.conf file with two SSL info updated – &lt;/P&gt;

&lt;P&gt;[tcpout-server://10.11.12.13:9997]&lt;BR /&gt;
sslRootCAPath = $SPLUNK_HOME/etc/certs/myCACertificate1.pem&lt;BR /&gt;
sslCertPath = $SPLUNK_HOME/etc/certs/myServerCertificate1.pem&lt;BR /&gt;
sslPassword = server_privkey_password&lt;BR /&gt;
sslVerifyServerCert = true&lt;BR /&gt;
sslCommonNameToCheck = phobos&lt;/P&gt;

&lt;P&gt;[tcpout-server://10.11.12.14:9997]&lt;BR /&gt;
sslRootCAPath = $SPLUNK_HOME/etc/certs/myCACertificate2.pem&lt;BR /&gt;
sslCertPath = $SPLUNK_HOME/etc/certs/myServerCertificate2.pem&lt;BR /&gt;
sslPassword = server_privkey_password&lt;BR /&gt;
sslVerifyServerCert = true&lt;BR /&gt;
sslCommonNameToCheck = deimos &lt;/P&gt;

&lt;P&gt;Ref - &lt;A href="https://wiki.splunk.com/Community:Splunk2Splunk_SSL_SelfSignedCert_NewRootCA" target="_blank"&gt;https://wiki.splunk.com/Community:Splunk2Splunk_SSL_SelfSignedCert_NewRootCA&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;===================================================================&lt;/P&gt;

&lt;P&gt;After Certificate renewal - &lt;/P&gt;

&lt;P&gt;Indexer1(IP - 10.11.12.13)       ------------------                     Indexer2  (IP-10.11.12.14)&lt;BR /&gt;
Inputs.conf (SSL-Cert-2)           ---------------------                    inputs.conf (SSL- Cert 2)&lt;/P&gt;

&lt;P&gt;UF1                                                                        UF2&lt;BR /&gt;
outputs.conf file with two SSL info updated – &lt;/P&gt;

&lt;P&gt;[tcpout:splunkssl]&lt;BR /&gt;
server = 10.11.12.13:9997, 10.11.12.14:9997&lt;BR /&gt;
compressed = true&lt;BR /&gt;
sslVerifyServerCert = false&lt;BR /&gt;
sslRootCAPath = $SPLUNK_HOME/etc/certs/myCACertificate2.pem&lt;BR /&gt;
sslCertPath = $SPLUNK_HOME/etc/certs/myServerCertificate2.pem&lt;BR /&gt;
sslPassword = password&lt;/P&gt;

&lt;P&gt;===================================================================&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 14:34:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362395#M9074</guid>
      <dc:creator>inventsekar</dc:creator>
      <dc:date>2020-09-29T14:34:03Z</dc:date>
    </item>
    <item>
      <title>Re: two SSL Certificates on a single indexer / forwarder</title>
      <link>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362396#M9075</link>
      <description>&lt;OL&gt;
&lt;LI&gt;&lt;P&gt;Yes you can deploy more than 1 ssl cert on a single indexer (on different ports)&lt;/P&gt;

&lt;H1&gt;Inputs.conf &lt;/H1&gt;

&lt;P&gt;[splunktcp-ssl:9997]&lt;BR /&gt;
serverCert = /path/to/port/9997/cert&lt;BR /&gt;
sslPassword = /path/to/port/9997/cert/key&lt;BR /&gt;
sslCommonNameToCheck = forwarderCertCommonNames&lt;BR /&gt;
compressed = true&lt;/P&gt;

&lt;P&gt;[splunktcp-ssl:9998]&lt;BR /&gt;
serverCert = /path/to/port/9998/cert&lt;BR /&gt;
sslPassword = /path/to/port/9998/cert/key&lt;BR /&gt;
sslCommonNameToCheck = forwarderCertCommonNames&lt;BR /&gt;
compressed = true&lt;/P&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;P&gt;Yes you can configure a forwarder to use two certs.  Please note splunk will switch between the two often (aka auto load balance, but if one is down it will stick to whatever is up).&lt;/P&gt;

&lt;H1&gt;Outputs.conf (on forwarders):&lt;/H1&gt;

&lt;P&gt;[tcpout]&lt;BR /&gt;
defaultGroup = secureIndexers&lt;/P&gt;

&lt;P&gt;[tcpout:secureIndexers]&lt;BR /&gt;
servers=10.11.12.13:9997, 10.11.12.14:9997&lt;/P&gt;

&lt;P&gt;[tcpout-server://10.11.12.13:9997]&lt;BR /&gt;
sslRootCAPath = $SPLUNK_HOME/etc/certs/myCACertificate1.pem&lt;BR /&gt;
sslCertPath = $SPLUNK_HOME/etc/certs/myServerCertificate1.pem&lt;BR /&gt;
sslPassword = server_privkey_password&lt;BR /&gt;
sslVerifyServerCert = true&lt;BR /&gt;
sslCommonNameToCheck = phobos&lt;BR /&gt;
compressed = true&lt;/P&gt;

&lt;P&gt;[tcpout-server://10.11.12.14:9997]&lt;BR /&gt;
sslRootCAPath = $SPLUNK_HOME/etc/certs/myCACertificate2.pem&lt;BR /&gt;
sslCertPath = $SPLUNK_HOME/etc/certs/myServerCertificate2.pem&lt;BR /&gt;
sslPassword = server_privkey_password&lt;BR /&gt;
sslVerifyServerCert = true&lt;BR /&gt;
sslCommonNameToCheck = deimos&lt;BR /&gt;
compressed = true&lt;/P&gt;

&lt;H1&gt;Inputs.conf (on Indexer named phobos)&lt;/H1&gt;

&lt;P&gt;[splunktcp-ssl:9997]&lt;BR /&gt;
serverCert = /path/to/phobos/cert&lt;BR /&gt;
sslPassword = /path/to/phobos/cert/key&lt;BR /&gt;
sslCommonNameToCheck = forwarderCertCommonNames&lt;BR /&gt;
compressed = true&lt;/P&gt;

&lt;H1&gt;Inputs.conf (on Indexer named deimos)&lt;/H1&gt;

&lt;P&gt;[splunktcp-ssl:9997]&lt;BR /&gt;
serverCert = /path/to/deimos/cert&lt;BR /&gt;
sslPassword = /path/to/deimos/cert/key&lt;BR /&gt;
sslCommonNameToCheck = forwarderCertCommonNames&lt;BR /&gt;
compressed = true&lt;/P&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;P&gt;How to test your certs are good:&lt;/P&gt;

&lt;P&gt;Verifying SSL Certificates on Remote / Local Machines&lt;BR /&gt;
This will test the entire certificate chain to see if it’s verifiable or not.&lt;/P&gt;

&lt;P&gt;openssl s_client -connect {server}:{port}&lt;/P&gt;

&lt;P&gt;Port 8000, 8060, 8089, 9998, etc.&lt;/P&gt;

&lt;P&gt;results should end with something like this:&lt;BR /&gt;
    Verify return code: 0 (ok)&lt;BR /&gt;
    ---&lt;BR /&gt;
if there are any errors above, the ssl cert will not validate/verify and the certificate will not be trusted&lt;/P&gt;&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;3.b. Verifying Completed Certificate (CER, CRT, or PEM) Matches Private or Public Keys&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;openssl x509  -noout -modulus -in {servername}.{yourdomain}.{yourtld}.{cer/crt/pem}| openssl md5
(stdin)= {MATCHING HASH}
openssl rsa -noout -modulus -in {servername}.{yourdomain}.{yourtld}.private.key | openssl md5
Enter pass phrase for {servername}.{yourdomain}.{yourtld}.private.key:
(stdin)= {MATCHING HASH}
openssl rsa -noout -modulus -in {servername}.{yourdomain}.{yourtld}.public.key  | openssl md5
(stdin)= {MATCHING HASH}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;So perhaps the most robust design would be 4 certs per forwarder, 2 certs per indexer:&lt;/P&gt;

&lt;P&gt;indexer1:9997 - Expires in 1 year&lt;BR /&gt;
indexer1:9998 - Expires in 2 years&lt;BR /&gt;
indexer2:9997 - Expires in 1 year&lt;BR /&gt;
indexer2:9998 - Expires in 2 years&lt;/P&gt;

&lt;P&gt;So that when one set expires, there are still two secure paths to indexers to fall back on.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 14:34:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362396#M9075</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2020-09-29T14:34:23Z</dc:date>
    </item>
    <item>
      <title>Re: two SSL Certificates on a single indexer / forwarder</title>
      <link>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362397#M9076</link>
      <description>&lt;P&gt;Hi Jkat54, much appreciated your reply.. let me test this. &lt;/P&gt;</description>
      <pubDate>Sat, 24 Jun 2017 02:07:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362397#M9076</guid>
      <dc:creator>inventsekar</dc:creator>
      <dc:date>2017-06-24T02:07:42Z</dc:date>
    </item>
    <item>
      <title>Re: two SSL Certificates on a single indexer / forwarder</title>
      <link>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362398#M9077</link>
      <description>&lt;P&gt;Another way we tried is to install another instance of Splunk in the same server during transition phase on another port. (eg .  splunk-instance-02). This helped us to completely isolate the complications and during the transition we moved all the new certificate connections to the new instance  and once everything has been updated, we shifted back to the original splunk instance&lt;/P&gt;

&lt;P&gt;high level steps&lt;BR /&gt;
- deployment-server-main (/opt/splunk   =&amp;gt; mgmt:8089) +  deployer-server-temporary (/opt/splunk2 =&amp;gt; mgmt:9089)  on same box&lt;BR /&gt;
- Deploy same etc/deployment-apps in both the instances&lt;BR /&gt;
- Push deployment-client app to the new certificate clients with  mgmt:9089&lt;BR /&gt;
- Get connectivity et.al working correctly&lt;BR /&gt;
- After all 100% servers migrated, just push a the "deployment-client" app with  mgmt:8089 address in it&lt;BR /&gt;
- viola everything works. Now delete /opt/splunk2 instance.&lt;/P&gt;</description>
      <pubDate>Sun, 25 Jun 2017 09:59:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362398#M9077</guid>
      <dc:creator>koshyk</dc:creator>
      <dc:date>2017-06-25T09:59:52Z</dc:date>
    </item>
    <item>
      <title>Re: two SSL Certificates on a single indexer / forwarder</title>
      <link>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362399#M9078</link>
      <description>&lt;P&gt;will be completing this in a day or two.. will update soon.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2017 04:30:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362399#M9078</guid>
      <dc:creator>inventsekar</dc:creator>
      <dc:date>2017-06-28T04:30:39Z</dc:date>
    </item>
    <item>
      <title>Re: two SSL Certificates on a single indexer / forwarder</title>
      <link>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362400#M9079</link>
      <description>&lt;P&gt;installing another splunk instance --- that looks like a good option, but can projects afford a separate server - is a big concern. well, anyhow, thanks for your idea. &lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2017 04:32:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362400#M9079</guid>
      <dc:creator>inventsekar</dc:creator>
      <dc:date>2017-06-28T04:32:18Z</dc:date>
    </item>
    <item>
      <title>Re: two SSL Certificates on a single indexer / forwarder</title>
      <link>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362401#M9080</link>
      <description>&lt;P&gt;I hope it all went well.  SSL deployments are always "fun"!&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2017 20:09:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362401#M9080</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2017-06-28T20:09:58Z</dc:date>
    </item>
    <item>
      <title>Re: two SSL Certificates on a single indexer / forwarder</title>
      <link>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362402#M9081</link>
      <description>&lt;P&gt;hi inventsekar, I mean within the SAME server as another splunk instance.  (/opt/splunk2). So you can keep the original instance isolated&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2017 14:25:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362402#M9081</guid>
      <dc:creator>koshyk</dc:creator>
      <dc:date>2017-06-29T14:25:28Z</dc:date>
    </item>
    <item>
      <title>Re: two SSL Certificates on a single indexer / forwarder</title>
      <link>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362403#M9082</link>
      <description>&lt;P&gt;i awarded the 50 points, and then i accepted as answer. &lt;BR /&gt;
they should have given instruction that - "when we accept as answer, the award points automatically will be given". &lt;BR /&gt;
sad part, i thought if i unaccept, the 50 points will be back to me, but unaccept works, but not the 50 points &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;now, only if @jkat54 award me back 50 points, i will get my 50. (i will accept this as an answer and he will get the 50)&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jul 2017 11:31:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362403#M9082</guid>
      <dc:creator>inventsekar</dc:creator>
      <dc:date>2017-07-06T11:31:16Z</dc:date>
    </item>
    <item>
      <title>Re: two SSL Certificates on a single indexer / forwarder</title>
      <link>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362404#M9083</link>
      <description>&lt;P&gt;Yeah no problem man.  Done.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jul 2017 12:06:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362404#M9083</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2017-07-06T12:06:38Z</dc:date>
    </item>
    <item>
      <title>Re: two SSL Certificates on a single indexer / forwarder</title>
      <link>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362405#M9084</link>
      <description>&lt;P&gt;Can we setup two different SSL cert's on same Indexer using same port and configure few Forwarders to use the new certs and other forwarders to use the existing SSL certs as per below plan?&lt;/P&gt;

&lt;P&gt;Current:&lt;BR /&gt;
SSL cert1 &amp;gt; 5 Indexers and all the Forwarders&lt;/P&gt;

&lt;P&gt;Test:&lt;BR /&gt;
SSL cert1 &amp;gt; 5 Indexers and 100 forwarders&lt;BR /&gt;
SSL cert2 &amp;gt; 5 Indexers and 50 forwarders&lt;/P&gt;

&lt;P&gt;After:&lt;BR /&gt;
SSL cert2 &amp;gt; 5 Indexers and 150 forwarders&lt;/P&gt;

&lt;P&gt;Please suggest if we have any process for this approach&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jul 2019 02:06:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362405#M9084</guid>
      <dc:creator>arrangineni</dc:creator>
      <dc:date>2019-07-19T02:06:18Z</dc:date>
    </item>
    <item>
      <title>Re: two SSL Certificates on a single indexer / forwarder</title>
      <link>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362406#M9085</link>
      <description>&lt;P&gt;Please post a new question.  You can point to this question in your new question if you like.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jul 2019 04:20:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/two-SSL-Certificates-on-a-single-indexer-forwarder/m-p/362406#M9085</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2019-07-19T04:20:51Z</dc:date>
    </item>
  </channel>
</rss>

