Hi Ajay, Thanks for reaching out.
I'm not an expert of that area - flow export is a core NiFi feature, however I think the reason encrypted properties being omitted during flow export is because only this way a flow can be made portable. Sensitive properties in flow are encrypted with a specific key belonging to that NiFi instance. So if an exported flow contains sensitive properties, the aforementioned key would need to be exported with that flow as well, which raises security concerns. Overall I would suggest using sensitive properties from parameter contexts. In that way you would also need to add the missing properties manually, however it would be easier as all properties were listed in one place in the exported flow json. Maybe someone who has better expertise in that part of NiFi can suggest a better approach, Regards Ferenc On Wed, Mar 6, 2024 at 3:06 PM Premarajan, Ajay <ajay.premara...@intelizign.com.invalid> wrote: > Hi Team, > > The nifi flow files when downloaded does not contain sensitive property > information. > https://issues.apache.org/jira/browse/NIFI-12644 was addressed to convert > nifi flow json to Minifi flow json. Since the sensitive properties are not > present in the nifi flow files, we have to add it manually before starting > MiNifi. > > What is the way to handle this scenario, will senstivie properties be > added to the Nifi flow files when downloaded or is there any approach for > this? > > I am enquiring this because we are doing an integration of MiNifi for > internal project. I would be happy to contribute for the solution. > > Kind Regard, > Ajay Premarajan > > > From: Premarajan, Ajay<mailto:ajay.premara...@intelizign.com> > Sent: Friday, March 1, 2024 7:31 AM > To: dev@nifi.apache.org<mailto:dev@nifi.apache.org> > Subject: Nifi flow json to MiNifi flow json 2.0.0.M2 > > Hi Team, > > I have a doubt regarding importing Nifi json flow to MiNifi json flow. > I am using code from https://github.com/apache/nifi/pull/8393 which was > used resolve https://issues.apache.org/jira/browse/NIFI-12644 issue. > > I have noticed that sensitive properties are not present when nifi flow > json is downloaded. How are these values passed to MiNifi for operation. > > For ex: > I have an InvokeHttp processor which uses SSL controller and has the > attribute “Request Username” and “Request Password” configured. When I > download the Nifi Flow json, the “Request Password” field is missing. Plus > the SSL controller donot have the password information in them. > > this is causing problem when I try to convert the Nifi flow json into > MiNifi flow json using the pull request code. > > Please suggest an way forward. > > > Regards, > Ajay Premarajan > > >
