Hi Jeremy,
MiNiFi constructs nifi.properties file from the config.yml located in ./conf
folder and this property needs to be set
manually in config.yml before the startup:
Security Properties:
Sensitive Props:
key: ''
Thanks,
Tom
From: Jeremy Pemberton-Pigott
Sent: 20 September 2021
Hi Tom,
I recall that I used the NiFi 1.14.0 binary to set the key and then copied
that over to the MiNiFi properties file to get it to work.
Linux only:
https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#updating-the-sensitive-properties-key
./bin/nifi.sh
Hi Bryan,
thanks for your feedback. Case b) is exactly what happened to us. After a clean
install containing only the official NARs and leaving our custom patches aside,
Nifi started without a problem.
Sorry for the noise,
Christian Gumpert
Leiter BI & Analytics
Lead Data Scientist
Product
ApacheCon @Home starts tomorrow! Details at
https://www.apachecon.com/acah2021/index.html
(Note: You're receiving this because you are subscribed to one or more
user lists for Apache Software Foundation projects.)
We've got three days of great content lined up for you, spanning 14
project
According to migration guidance for NiFi property 'Sensitive Properties Key'
should be generated at startup, I believe this is the same behaviour in case of
MiNiFi since they merged the codebase. Why is this happening?
BR,
Tom
From: Tomislav Novosel
Sent: 20 September 2021 11:05
To:
Hello,
The reason for the error about the properties being sensitive is due
to the ghost controller services... since a ghost controller service
means we are missing the real definition of the component, NiFi
doesn't know if the properties are actually sensitive or not, so it
makes all properties
Hi to all,
I was using MiNiFi 0.5.0 running on ubuntu, installed as a service.
I switched now to MiNiFi 1.14.0 - I disabled minifi service, deleted
installation folder and unpacked MiNiFi 1.14.0 folder at the same place
where was 0.5.0 installed.
I started new MiNiFi 1.14.0 and the service don't
