You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Andrew M. Lim (Jira)" <ji...@apache.org> on 2019/11/14 00:32:00 UTC
[jira] [Commented] (NIFI-6868) Sensitive parameters not evaluated
properly when executing processor that references one.
[ https://issues.apache.org/jira/browse/NIFI-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16973832#comment-16973832 ]
Andrew M. Lim commented on NIFI-6868:
-------------------------------------
I'm able to reproduce with the GetSFTP processor scenario described above, but not with GetTwitter. I was able to get results referencing a sensitive parameter for the Consumer key property.
> Sensitive parameters not evaluated properly when executing processor that references one.
> -----------------------------------------------------------------------------------------
>
> Key: NIFI-6868
> URL: https://issues.apache.org/jira/browse/NIFI-6868
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.10.0
> Reporter: Rob Fellows
> Priority: Major
>
> Configuring a processor with a sensitive property value set to reference a sensitive parameter does not evaluate properly.
>
> An easy way to reproduce this is to create a GetSFTP processor to use a sensitive parameter for the "password" property. You can use a publicly available SFTP server like:
>
> {{hostname: test.rebex.net}}
> {{password: password}}
>
> Connect this GetSFTP processor to an Add a LogMessage or some other processor and start the GetSFTP processor.
>
> When the password property is entered as a string of "password", it works.
> If you create a parameter in the parameter context, say password, and reference it as the property value, "#\{password}", you will see failures that it can not connect.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)