Hey Josef, I’m sorry about the trouble. It looks like this issue was reported here [1]. We are looking into a fix for it.
Fortunately, if you don’t want to wait for the fix there is a workaround available. The work around is to follow these steps: 1. Instead of jumping straight to 1.18, update first to 1.16.4 2. Start NiFi and wait for it to start up. Ensure that all looks healthy. 3. Shutdown NiFi 4. Upgrade to 1.18, ensuring that you copy over the conf/flow.json.gz file from 1.16.4 So essentially, you’d need to upgrade from 1.15 to 1.16, and then to 1.18. The reason this works is that prior to 1.16, we stored the flow in conf/flow.xml.gz. But in 1.16 we updated that to flow.json.gz - and also kept around flow.xml.gz in order to make this change seemless. But it looks like when Sensitive Dynamic Properties was added, there was a bug that caused us to not properly load things from flow.xml.gz, only from flow.json.gz. So, if you upgrade first to 1.16.4, you’ll end up with a flow.json.gz that you can then copy over to your 1.18 instance. I know this is not ideal, and I apologize for that. But if you’re looking to upgrade right away this will be quicker than waiting for a resolution of NIFI-10567. Thanks! -Mark [1] https://issues.apache.org/jira/browse/NIFI-10567 On Oct 13, 2022, at 8:28 AM, [email protected]<mailto:[email protected]> wrote: I just found this blog https://exceptionfactory.com/posts/2022/08/02/implementing-apache-nifi-support-for-sensitive-dynamic-properties/ about the jira ticket https://issues.apache.org/jira/browse/NIFI-9957?jql=text%20~%20%22sensitive%20dynamical%22 . What we found out it is that the controller DBCPConnectionPool is fine with the password as well as the invokeHTTP. So for the ones where sensitive dynamic properties has been enabled the migration of the password was successful, but not for the others… Cheers Josef From: "Zahner Josef, GSB-LR-TRW-LI" <[email protected]<mailto:[email protected]>> Date: Thursday, 13 October 2022 at 13:59 To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: NiFi 1.18.0 Sensitive Property broken after Upgrade Hi guys We just upgraded from NiFi 1.15.3 to 1.18.0. We have somehow a migration issue, it seems that all our sensitive properties are broken with 1.18.0. Check my screenshot below, It’s related to controller services as well as to processors. All sensitive properties shows us an error. If we replace the password it’s fine, so it seems that the password got corrupt due to the upgrade. Any hints? It leads to a ton of work, we have hundreds of processors with a hardcoded password… I’ve seen that we can use external password providers, do we have to migrate somehow? <image001.png> <image002.png> Cheers Josef
