Apache NIFI Authentication LDAP

@Ripul, Welcome to our community! To help you get the best possible answer, I have tagged in our NiFi experts  @hegdemahendra @MattWho, who may be able to assist you further.

Please feel free to provide any additional information or details about your query. We hope that you will find a satisfactory solution to your question.

@Ripul 

Welcome to the Cloudera Community!

Sharing a screenshot would be helpful here, but I am assume what you are seeing is something like this when you login with your admin user or other users:

This is because of an authorization issue. When NiFi is started for the first time it does not have a flow.josn.gz file yet which contains everything you see on the NiFi canvas.   So NiFi will generate that flow.josn.gz which will consist of just a root process group.

You'll notice on the cavas the above "Operation" panel.  It  will show the current selected component on the canvas.  With nothing selected on the canvas, it will show details for whichever NiFi Process Group you are currently displaying.  Since this is a new install, what the Operation panel is showing is this generated root process group.  Anytime you see the name as just the UUID for a component, it indicates the currently authenticated user is not authorized to view that component.  A greyed out "gear" (configuration) icon indicates user is not authorized to modify the component.  A greyed out "key" (Access Policies) icon indicates currently authenticated user is not authorized to view and maybe modify policies (authorizations) in that component.

NiFi provides very granular authorization control all the way down to the individual component level.  This may sound like a lot to need to manage; however, there is policy inheritance in place.  Example:  You add a processor to the canvas. If not explicit policy is defined on the processor itself it will inherit policy from the process group it is inside.  If there is no policy defined on the process group, it will inherit  policy from parent process group.  At the very top level is the above mentioned parent process group.  So setting policies on the parent process group will control access on everything added to cavas until ab explicit access policy is set on a sub component.

There are also global policies that can be setup and your "admin" user should have been setup on a number of these.

From the above global menu found in upper right corner you should see that "Policies" is not greyed out for your admin user.  Within global  "Policies", all users need to be granted "view the user interface" in order to access the user interface, so it sounds like you have already done this for other users.  Your "admin" user should also have "access all policies" (view and modify) which allows that user to view and modify access policies (authorizations) on every component anywhere on the canvas.   This policy is what makes the "key" icon not greyed out on the "Operation" panel mentioned earlier.


So to give select users (including your admin user) the ability to add components to the root process group, your admin user will need to select the key icon on the root process group and grant those users:

Once your admin user and other users are properly authorized to "view the component", the Operate panel will show the process group name instead of just the process group assigned UUID.

The gear icon will not be greyed out once your admin user and other users have "modify the component".    "Modify the component" on a process group will also allow added users to see the component adding icon a the top of the UI.

I am not going to cover all the NiFi Policies, but they can be found in the NiFi Administration guide under Configuring Users & Access Policies

Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped.

Thank you,
Matt