You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@nifi.apache.org by Kyle Richardson <ky...@gmail.com> on 2017/08/18 13:33:20 UTC

Sensitive Properties

Is there a safe way to set nifi.sensitive.props.key after having setup
processors with sensitive property values? The value is currently blank
(default) but I'd like to set it without breaking all of my existing flows.
Is it as simple as reentering the sensitive property values after a service
restart?

Any guidance or experience with this would be appreciated.

Thanks,
Kyle

Re: Sensitive Properties

Posted by Kyle Richardson <ky...@gmail.com>.

Thanks, Bryan! Exactly what I was looking for. Much appreciated.

-Kyle

On Fri, Aug 18, 2017 at 11:54 AM Bryan Bende <bb...@gmail.com> wrote:

> Kyle,
>
> Great question...
>
> If you change the sensitive properties key and restart NiFi when there
> are already previously encrypted properties, it will fail to start and
> say that it couldn't decrypt the values.
>
> The way to change the key is by using the NiFi toolkit which has a
> tool specifically to migrate the flow.xml.gz from one key to another.
>
> This section of the admin guide describes its usage:
>
> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#existing-flow-migration
>
> Thanks,
>
> Bryan
>
>
> On Fri, Aug 18, 2017 at 9:33 AM, Kyle Richardson
> <ky...@gmail.com> wrote:
> > Is there a safe way to set nifi.sensitive.props.key after having setup
> > processors with sensitive property values? The value is currently blank
> > (default) but I'd like to set it without breaking all of my existing
> flows.
> > Is it as simple as reentering the sensitive property values after a
> service
> > restart?
> >
> > Any guidance or experience with this would be appreciated.
> >
> > Thanks,
> > Kyle
>

Re: Sensitive Properties

Posted by Bryan Bende <bb...@gmail.com>.

Kyle,

Great question...

If you change the sensitive properties key and restart NiFi when there
are already previously encrypted properties, it will fail to start and
say that it couldn't decrypt the values.

The way to change the key is by using the NiFi toolkit which has a
tool specifically to migrate the flow.xml.gz from one key to another.

This section of the admin guide describes its usage:
https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#existing-flow-migration

Thanks,

Bryan

On Fri, Aug 18, 2017 at 9:33 AM, Kyle Richardson
<ky...@gmail.com> wrote:
> Is there a safe way to set nifi.sensitive.props.key after having setup
> processors with sensitive property values? The value is currently blank
> (default) but I'd like to set it without breaking all of my existing flows.
> Is it as simple as reentering the sensitive property values after a service
> restart?
>
> Any guidance or experience with this would be appreciated.
>
> Thanks,
> Kyle