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]

Support Questions

Find answers, ask questions, and share your expertise
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

NiFi - restricted processors won't start (REST-API, NiFi Toolkit)

avatar
Master Collaborator

I have a process-group which has to be started via rest-api.

Principial it works to start the process-group but processors inside which are marked as "restricted" won't get started, f.e. ExecuteScript, PutFile. These processors remain stopped. No error message. In nifi-app.log are only the started processors listed. No word of the others.

In the UI of course I can start these processors.

How to solve this via rest-api? Thanks for any help.

Using NiFi 1.9.2


SUPPLEMENT

It is not a REST-API thing.

Tried with NiFi Toolkit (/bin/cli.sh nifi pg-start -pgid 708358fc-016c-1000-0000-00000bf....). All processors get started excepted the restricted ones.


So where is the cause and how to fix this?

1 ACCEPTED SOLUTION

avatar
Master Collaborator

Solved
Cluster-node users (who obviously execute these actions via rest-api or toolkit cli) had no permission to work with restricted components.
Added permission, startet NiFi new and it works.

Would by helpfull if somewhere a message would come up to tell that this is an authorization problem...

View solution in original post

1 REPLY 1

avatar
Master Collaborator

Solved
Cluster-node users (who obviously execute these actions via rest-api or toolkit cli) had no permission to work with restricted components.
Added permission, startet NiFi new and it works.

Would by helpfull if somewhere a message would come up to tell that this is an authorization problem...