<?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>question Re: NiFi Error Despite Successful SSL Handshake using openssl s_client in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/NiFi-Error-Despite-Successful-SSL-Handshake-using-openssl-s/m-p/289366#M214202</link>
    <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/73987"&gt;@JC_ROS&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;With a secured NiFi all actions are authenticated and authorized.&amp;nbsp; Thus mutual TLS authentication is required for NiFi things like:&lt;BR /&gt;&lt;BR /&gt;1. Node to Node communications (Older versions of NiFi had ability to set NeedClientAuth=false in the nifi.properties to make node to node comms 1-way TLS.&amp;nbsp; Newer NiFi releases removed this property resulting in mutual TLS being required here.&lt;BR /&gt;2. NiFi Remote Process Groups (RPG) - The S2S protocol used by the RPG required mutual TLS.&amp;nbsp; The NiFI instance running the RPG is acting as a client and must present a clientAuth certificate.&lt;BR /&gt;3. NiFi load balanced connections&lt;BR /&gt;&lt;BR /&gt;The above all utilize the NiFi node keystore and truststore.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;</description>
    <pubDate>Fri, 07 Feb 2020 16:50:55 GMT</pubDate>
    <dc:creator>MattWho</dc:creator>
    <dc:date>2020-02-07T16:50:55Z</dc:date>
  </channel>
</rss>

