<?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 and NiFi Registry authentication error in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/NiFi-and-NiFi-Registry-authentication-error/m-p/204726#M166715</link>
    <description>&lt;P&gt;You will need machine names (DN) for both Nifi and Nifi Registry like "CN=machinename,...dc=example,dc=com" where in CN you will use server name the remaining portion will come under whatever wildcard (sub)domain you have.&lt;/P&gt;&lt;P&gt;Then you will enter the full DN, manually as a user in both Nifi and Nifi Registry. This method is similar to when setting up site-to-site policies here:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.hortonworks.com/articles/88473/site-to-site-communication-between-secured-https-a.html" target="_blank"&gt;https://community.hortonworks.com/articles/88473/site-to-site-communication-between-secured-https-a.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Finally, you can check logs files for errors when pulling buckets in both Nifi and Nifi registry in files *-app.log and *-user.log, this may as well give you a full DN Nifi is looking for.&lt;/P&gt;</description>
    <pubDate>Tue, 29 May 2018 21:05:47 GMT</pubDate>
    <dc:creator>umair_khan</dc:creator>
    <dc:date>2018-05-29T21:05:47Z</dc:date>
  </channel>
</rss>

