- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
NiFi - restricted processors won't start (REST-API, NiFi Toolkit)
- Labels:
-
Apache NiFi
Created on 08-08-2019 03:50 PM - edited 09-16-2022 07:32 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
Created 08-10-2019 11:52 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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...
Created 08-10-2019 11:52 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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...
