<?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 Do we have to enable/configure SSL on our 6.4.3 UFs before we upgrade to 7.1.2? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Do-we-have-to-enable-configure-SSL-on-our-6-4-3-UFs-before-we/m-p/391622#M69984</link>
    <description>&lt;P&gt;We are upgrading our Splunk Indexer from 6.4.3 to 7.1.2 (via 6.5).  Our forwarders are running a mixture of 6.2.4 and 6.4.3 and are NOT using SSL. &lt;BR /&gt;
Then I noticed this compatibility matrix for the UFs: &lt;A href="http://docs.splunk.com/Documentation/Forwarder/7.1.2/Forwarder/Compatibilitybetweenforwardersandindexers"&gt;http://docs.splunk.com/Documentation/Forwarder/7.1.2/Forwarder/Compatibilitybetweenforwardersandindexers&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;If I read this correctly, does this mean we must enable/configure SSL on our 6.4.3 UFs before we upgrade? Or will we still be able to send data to the 7.1.2 indexer without SSL from the older UFs? &lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Thu, 02 Aug 2018 21:32:57 GMT</pubDate>
    <dc:creator>Branden</dc:creator>
    <dc:date>2018-08-02T21:32:57Z</dc:date>
    <item>
      <title>Do we have to enable/configure SSL on our 6.4.3 UFs before we upgrade to 7.1.2?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Do-we-have-to-enable-configure-SSL-on-our-6-4-3-UFs-before-we/m-p/391622#M69984</link>
      <description>&lt;P&gt;We are upgrading our Splunk Indexer from 6.4.3 to 7.1.2 (via 6.5).  Our forwarders are running a mixture of 6.2.4 and 6.4.3 and are NOT using SSL. &lt;BR /&gt;
Then I noticed this compatibility matrix for the UFs: &lt;A href="http://docs.splunk.com/Documentation/Forwarder/7.1.2/Forwarder/Compatibilitybetweenforwardersandindexers"&gt;http://docs.splunk.com/Documentation/Forwarder/7.1.2/Forwarder/Compatibilitybetweenforwardersandindexers&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;If I read this correctly, does this mean we must enable/configure SSL on our 6.4.3 UFs before we upgrade? Or will we still be able to send data to the 7.1.2 indexer without SSL from the older UFs? &lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 02 Aug 2018 21:32:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Do-we-have-to-enable-configure-SSL-on-our-6-4-3-UFs-before-we/m-p/391622#M69984</guid>
      <dc:creator>Branden</dc:creator>
      <dc:date>2018-08-02T21:32:57Z</dc:date>
    </item>
    <item>
      <title>Re: Do we have to enable/configure SSL on our 6.4.3 UFs before we upgrade to 7.1.2?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Do-we-have-to-enable-configure-SSL-on-our-6-4-3-UFs-before-we/m-p/391623#M69985</link>
      <description>&lt;P&gt;Non-SSL forwarding is still supported but if you do decide to use SSL at some point, you'll have to work out the version/cipher compatibility between UF and Indexer. Your configuration should work just fine the way it is.&lt;/P&gt;

&lt;P&gt;If your UFs are configured as deployment clients and you're updating your Deployment Server, consider that the SSL/TLS config for the management port in 6.6+ is affected by the version/cipher changes and you'll need to work out a solution for that. The Known Issues page at &lt;A href="http://docs.splunk.com/Documentation/Splunk/7.1.2/ReleaseNotes/KnownIssues"&gt;http://docs.splunk.com/Documentation/Splunk/7.1.2/ReleaseNotes/KnownIssues&lt;/A&gt; suggests some configurations you could use on the server side to support legacy clients.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Aug 2018 22:01:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Do-we-have-to-enable-configure-SSL-on-our-6-4-3-UFs-before-we/m-p/391623#M69985</guid>
      <dc:creator>jtacy</dc:creator>
      <dc:date>2018-08-02T22:01:07Z</dc:date>
    </item>
  </channel>
</rss>

