<?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 Does Splunk Http Event Collector supports Server Name Indication (SNI)? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Does-Splunk-Http-Event-Collector-supports-Server-Name-Indication/m-p/567095#M100760</link>
    <description>&lt;P&gt;We have a requirement to collect the logs using client Certs (mTLS) authentication, and we are using Splunk HTTP Event Collector Endpoint along with token and client certs to achieve this.&amp;nbsp;&lt;/P&gt;&lt;P&gt;So in order to achieve extension to this TLS support we would like to know is there any way to update the .conf files to support the multiple server-side certificates which can be used for Server Name Indication (SNI)&amp;nbsp;&lt;SPAN&gt;by which a&amp;nbsp;client&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;indicates which&amp;nbsp;hostname&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;it is attempting to connect.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Have someone tried a similar approach before? Also if you could give other suggestions for our solution will be much appreciated!&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;Amit R. S&lt;/P&gt;</description>
    <pubDate>Wed, 15 Sep 2021 11:12:47 GMT</pubDate>
    <dc:creator>amshukla</dc:creator>
    <dc:date>2021-09-15T11:12:47Z</dc:date>
    <item>
      <title>Does Splunk Http Event Collector supports Server Name Indication (SNI)?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-Splunk-Http-Event-Collector-supports-Server-Name-Indication/m-p/567095#M100760</link>
      <description>&lt;P&gt;We have a requirement to collect the logs using client Certs (mTLS) authentication, and we are using Splunk HTTP Event Collector Endpoint along with token and client certs to achieve this.&amp;nbsp;&lt;/P&gt;&lt;P&gt;So in order to achieve extension to this TLS support we would like to know is there any way to update the .conf files to support the multiple server-side certificates which can be used for Server Name Indication (SNI)&amp;nbsp;&lt;SPAN&gt;by which a&amp;nbsp;client&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;indicates which&amp;nbsp;hostname&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;it is attempting to connect.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Have someone tried a similar approach before? Also if you could give other suggestions for our solution will be much appreciated!&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;Amit R. S&lt;/P&gt;</description>
      <pubDate>Wed, 15 Sep 2021 11:12:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-Splunk-Http-Event-Collector-supports-Server-Name-Indication/m-p/567095#M100760</guid>
      <dc:creator>amshukla</dc:creator>
      <dc:date>2021-09-15T11:12:47Z</dc:date>
    </item>
  </channel>
</rss>

