nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Grande <agra...@hortonworks.com>
Subject Re: Sensitive values
Date Wed, 04 May 2016 11:36:36 GMT
Ravi,

As Simon mentioned, the current behavior is an intentional design choice. Typically one would
set properties like these in different environment, but not retrieve them.

Take a look at https://github.com/aperepel/nifi-api-deploy for an example of how applying
environment-specific properties can be applied on deploy.

Andrew




On 5/4/16, 7:33 AM, "Simon Ball" <sball@hortonworks.com> wrote:

>This is a deliberate behavior to protect sensitive values being placed in templates. The
chances are that if you’re using templates to move flows between instances, the instances
would be configured with a different key for encrypting sensitive values, so even if you were
to include the value in the template it would not be portable. 
>
>A possible solution would be to use the template to deploy, and then an API call to update
the sensitive values.
>
>Simon
>
>
>> On May 4, 2016, at 8:37 AM, Ravisankar Mani <rravimr@gmail.com> wrote:
>> 
>> Hi All,
>> 
>> I have created a specific template. In this template, some of the processors contains
sensitive values(Like password, DBCP connection pool contains connection password credentials)
. 
>> 
>> The sensitive values gets resets when i reuse the saved template or create a instance
template through rest api. Is there possible to disable the above mention behavior ? Please
share your concern on this.
>> 
>> 
>> Regards,
>> Ravisankar
>
Mime
View raw message