Blocking start/stop on the entire process group

[#1]

Hello!

Is there a way to stop the start/stop requests on the entire process group. Sometimes, I am clicking by mistake outside of a processor, and start/stop all the processor inside of a process group. I am trying to find a way to stop this happening.

Do you know a way that I can modify something in the web server properties that will block all those requests of nifi-api?

I was thinking also of a reverse proxy method that will block those request, but I want to know first if there is a way to involve only NiFi.

Thank you!

[#2]

@alexduta Welcome to the Cloudera Community!

To help you get the best possible solution, I have tagged our NiFi experts @steven-matison @Wynner  who may be able to assist you further.

Please keep us updated on your post, and we hope you find a satisfactory solution to your query.

[#3]

@alexduta 
NiFi's authorization policies control what users can and can't interact with within the NiFi UI.  If the user has been granted "modify the component" or "operate the component" policies on the processors or process group, the user will be able to initiate a start or stop of the process group.

Of course the user needs "view the component" and "modify the component" on a process group in order to even add components to the process group. 

Apache NiFi does not provide a way to disable start/stop from the process group level through any configuration file properties.

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

Thank you,
Matt

[#4]

@alexduta Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks.