inc.net<http://acesinc.net/>
http://everwatchsolutions.com<http://everwatchsolutions.com/>
From: Daniel Chaffelson
Reply-To: "users@nifi.apache.org"
Date: Saturday, November 7, 2020 at 2:40 PM
To: "users@nifi.apache.org"
Subject: Re: enhancemen
//everwatchsolutions.com
>
>
>
> *From: *Bryan Bende
> *Reply-To: *"users@nifi.apache.org"
> *Date: *Wednesday, November 4, 2020 at 5:22 PM
> *To: *"users@nifi.apache.org"
> *Subject: *Re: enhancement request for NiFi variable registry support on
> SSLConte
mber 4, 2020 at 5:22 PM
To: "users@nifi.apache.org"
Subject: Re: enhancement request for NiFi variable registry support on
SSLContextServices --> parameter contexts
They are currently stored in the flow and encrypted the same way as sensitive
properties. There has been discussion arou
They are currently stored in the flow and encrypted the same way as
sensitive properties. There has been discussion around sourcing sensitive
parameters from external systems like Vault, but I’m not aware of anyone
working on it. I could see value binding to external files, but also not
sure of
Hi Bryan,
Thank you for pointing me to parameter contexts as a possible answer to a
shortcoming we deal w/ for reasons of some challenges in handling different
environments with their different constraints and limitations we deal w/ for
those environments. I’ve glanced at the parameter
