Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 05-21-2018 12:14 PM


I am getting error Untrusted proxy CN=rang2, OU=NIFI while trying to log into NiFi UI .
Follow this page I enable SSL for Nifi ,but meet one mistake as he say and can't solve it by myself.
https://community.hortonworks.com/articles/58009/hdf-20-enable-ssl-for-apache-nifi-from-ambari.html
In Ambari UI, I've set Node Identities in Advanced nifi-ambari-ssl-config:
<!-- Provide the identity (typically a DN) of each node when clustered (see tool tip for detailed description of Node Identity). Must be specified when Ranger Nifi plugin will not be used for authorization. --> <property name="Node Identity 1">CN=rang2, OU=NIFI</property>
And in authorizers.xml, it seems to work:
<authorizer>
<identifier>ranger-provider</identifier>
<class>org.apache.nifi.ranger.authorization.RangerNiFiAuthorizer</class>
<property name="Ranger Audit Config Path">/usr/hdf/current/nifi/conf/ranger-nifi-audit.xml</property>
<property name="Ranger Security Config Path">/usr/hdf/current/nifi/conf/ranger-nifi-security.xml</property>
<property name="Ranger Service Type">nifi</property>
<property name="Ranger Application Id">nifi</property>
<property name="Ranger Admin Identity">CN=mytest, OU=NIFI</property>
<property name="Ranger Kerberos Enabled">true</property>
<!-- Provide the identity (typically a DN) of each node when clustered (see tool tip for detailed description of Node Identity). Must be specified when Ranger Nifi plugin will not be used for authorization. -->
<property name="Node Identity 1">CN=rang2, OU=NIFI</property>
</authorizer>
</authorizers>
But this error happened when I set policies by Ranger UI and try to login nifi. Any suggestions?
Created 05-21-2018 07:30 PM
The "<propertyname="Node Identity 1">CN=rang2, OU=NIFI</property>" property in the authorizers.xml is only used when using NiFi's default file based authorization provider. It does not apply when using Ranger as your authorization provider.
-
In Ranger, you will need to make sure the user "CN=rang2, OU=NIFI" exists and has been give access to the "/proxy" NiFi Resource Identifier.
-
Thank you,
Matt
-
If you found this answer addressed your question, please take moment to login and click "accept" below the answer.
Created 05-21-2018 07:30 PM
The "<propertyname="Node Identity 1">CN=rang2, OU=NIFI</property>" property in the authorizers.xml is only used when using NiFi's default file based authorization provider. It does not apply when using Ranger as your authorization provider.
-
In Ranger, you will need to make sure the user "CN=rang2, OU=NIFI" exists and has been give access to the "/proxy" NiFi Resource Identifier.
-
Thank you,
Matt
-
If you found this answer addressed your question, please take moment to login and click "accept" below the answer.
Created 05-22-2018 02:00 AM
Thanks, followed your advice I've solved this problem. I didn't realize that nifi host should also authoried by Ranger.