@Simran Kaur All ports 1024 and below are considered reserved as privileged ports and can be only used/bound to by process run by the root user. NiFi can use these ports if it is running as the root user. The alternative is to setup your ListenHTTP processor to run on a non privileged port and then set up port forwarding in your iptables to redirect incoming requests to a privileged port to that non privileged port you are using in NiFi: iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-ports 8081 Thanks, ... View more

@Bhushan Babar I am not a NiFi developer, so if you are looking for way to modify the existing NiFi code to programmatically create new users in NiFi's authorizer and grant them access, I am not going to be able to help there. NiFi's default file-based authorizer supports groups. You can create 1 or more groups and assign those groups all the global access policies and all the root process group component level policies. Then whenever you create a new user, simply add them to those groups during user creation and they will have access to those resources. The typical process here is to create an admin group (has most policies), Dataflow Manger group (has policies that give these users the ability to add to and modify dataflows, access the data and access provenance), Dataflow viewers (has polices that only give view access to the dataflows), Site-to-site group (has policies related to Site-to-site Components), and Proxy group (has proxy policy granted to Nifi nodes and any external proxy server). Programmatically i would think what you are looking to do would be difficult to implement. NiFi authenticates user via certificates and/or multiple other methods (LDAP or kerberos). This means that servers that connect to your NiFi with a valid certificate would be automatically given admin level access (all policies)? Some policies are very specific to servers and not users (proxy and site-to-site policies for example). Some policies are not even available until an associated component that uses that policy is added to the canvas (Site-to-Site remote input or output ports). Thanks, Matt ... View more

@Anishkumar Valsalam In a Nifi cluster you need to make sure you have uploaded you new custom component nars to every node in the cluster. I do not recommend adding your custom nars directly to the existing NiFi lib directory. While this works, it can become annoying to manage when you upgrade NiFi versions. NiFi allows you to specify an additional lib directory where you can place your custom nars. Then if you upgrade, the new version can just get pointed at this existing additional lib dir. Adding additional lib directories to your NiFi is as simple adding an additional property to the nifi.properties file. for example: nifi.nar.library.directory.lib1=/nars-custom/lib1 nifi.nar.library.directory.lib2=/nars-custom/lib2 Note: Each prefix must be unique (i.e. - lib1 and lib2 in the above examples). These lib directories must be accessible by the user running your NiFi instance. Thanks, Matt ... View more