Thank you very much @Bryan Bende for your valuable inputs. I finally got it working by following your suggestion. Here is my working authorizers.xml <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <authorizers> <userGroupProvider> <identifier>file-user-group-provider</identifier> <class>org.apache.nifi.authorization.FileUserGroupProvider</class> <property name="Users File">./conf/users.xml</property> <property name="Legacy Authorized Users File"></property> <property name="Initial User Identity 1">CN=node1-nifi.jp.local, OU=NIFI</property> <property name="Initial User Identity 2">CN=node2-nifi.jp.local, OU=NIFI</property> <property name="Initial User Identity 3">cn=admin,ou=users,dc=nifi,dc=ldap,dc=jp</property> </userGroupProvider> <accessPolicyProvider> <identifier>file-access-policy-provider</identifier> <class>org.apache.nifi.authorization.FileAccessPolicyProvider</class> <property name="User Group Provider">file-user-group-provider</property> <property name="Authorizations File">./conf/authorizations.xml</property> <property name="Initial Admin Identity">cn=admin,ou=users,dc=nifi,dc=ldap,dc=jp</property> <property name="Legacy Authorized Users File"></property> <property name="Node Identity 1">CN=node1-nifi.jp.local, OU=NIFI</property> <property name="Node Identity 2">CN=node2-nifi.jp.local, OU=NIFI</property> <property name="Node Identity 3">cn=admin,ou=users,dc=nifi,dc=ldap,dc=jp</property> </accessPolicyProvider> <authorizer> <identifier>managed-authorizer</identifier> <class>org.apache.nifi.authorization.StandardManagedAuthorizer</class> <property name="Access Policy Provider">file-access-policy-provider</property> </authorizer> </authorizers> Apart from the above changes, I have modified identity mapping pattern in nifi.properties nifi.security.identity.mapping.pattern.dn=^cn=(.*?),ou=(.*?),dc=(.*?),dc=(.*?),dc=(.*?)$ nifi.security.identity.mapping.value.dn=$1 Thanks again! ... View more

@Andrew thomas Once you have a NiFi cluster installed and running, any change you make within the NiFi Ui affects every node in the cluster. There is no way in a NiFi cluster to deploy a flow to just one node only. There is no need to stop any existing running flow within the UI when you are adding/building new flows within the same UI. Any configuration changes that affect any one of NiFi's configuration files (except logback.xml) will require a NiFi restart before those changes will take affect. Thank you, Matt ... View more