<?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 Secure Nifi Registry Errors in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Secure-Nifi-Registry-Errors/m-p/220686#M74737</link>
    <description>&lt;P&gt;Following the tutorials &lt;A href="https://community.hortonworks.com/content/kbentry/170966/setting-up-a-secure-apache-nifi-registry.html"&gt;Setting Up a Secure Nifi Registry&lt;/A&gt; and &lt;A href="https://community.hortonworks.com/articles/171173/setting-up-a-secure-nifi-to-integrate-with-a-secur.html"&gt;Secure Nifi to integrate with secure Nifi Registry&lt;/A&gt;, I'm not able to start nifi registry. I tried a lot of different configuration, also those I used to secure nifi. We don't use ldap or kerberos.&lt;/P&gt;&lt;P&gt;Every constellation ends up with an error messages like &lt;/P&gt;&lt;P&gt;'Caused by: org.apache.nifi.registry.security.authorization.AuthorizerFactoryException: When running securely, the authorizer identifier must be specified in the nifi properties file'&lt;/P&gt;&lt;P&gt;We work with windows / windows server, nifi 1.5.0 and nifi registry 0.1.0. Nifi registry runs (unsecured), and nifi runs secured, after using some tricks (I have to go through 2 phases to get it running, but it is repeatable, so I can go with this..)&lt;/P&gt;&lt;P&gt;Any suggestions ?&lt;/P&gt;</description>
    <pubDate>Tue, 20 Feb 2018 00:33:34 GMT</pubDate>
    <dc:creator>martin_keller</dc:creator>
    <dc:date>2018-02-20T00:33:34Z</dc:date>
    <item>
      <title>Secure Nifi Registry Errors</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Secure-Nifi-Registry-Errors/m-p/220686#M74737</link>
      <description>&lt;P&gt;Following the tutorials &lt;A href="https://community.hortonworks.com/content/kbentry/170966/setting-up-a-secure-apache-nifi-registry.html"&gt;Setting Up a Secure Nifi Registry&lt;/A&gt; and &lt;A href="https://community.hortonworks.com/articles/171173/setting-up-a-secure-nifi-to-integrate-with-a-secur.html"&gt;Secure Nifi to integrate with secure Nifi Registry&lt;/A&gt;, I'm not able to start nifi registry. I tried a lot of different configuration, also those I used to secure nifi. We don't use ldap or kerberos.&lt;/P&gt;&lt;P&gt;Every constellation ends up with an error messages like &lt;/P&gt;&lt;P&gt;'Caused by: org.apache.nifi.registry.security.authorization.AuthorizerFactoryException: When running securely, the authorizer identifier must be specified in the nifi properties file'&lt;/P&gt;&lt;P&gt;We work with windows / windows server, nifi 1.5.0 and nifi registry 0.1.0. Nifi registry runs (unsecured), and nifi runs secured, after using some tricks (I have to go through 2 phases to get it running, but it is repeatable, so I can go with this..)&lt;/P&gt;&lt;P&gt;Any suggestions ?&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2018 00:33:34 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Secure-Nifi-Registry-Errors/m-p/220686#M74737</guid>
      <dc:creator>martin_keller</dc:creator>
      <dc:date>2018-02-20T00:33:34Z</dc:date>
    </item>
    <item>
      <title>Re: Secure Nifi Registry Errors</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Secure-Nifi-Registry-Errors/m-p/220687#M74738</link>
      <description>&lt;P&gt;Solved. It was probably an issue with the installed Java Version. After updating to jdk1.8.0_162 it worked.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2018 23:03:31 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Secure-Nifi-Registry-Errors/m-p/220687#M74738</guid>
      <dc:creator>martin_keller</dc:creator>
      <dc:date>2018-02-20T23:03:31Z</dc:date>
    </item>
  </channel>
</rss>

