[NIFI-6868] Sensitive parameters not evaluated properly when executing processor that references one.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.10.0
• Fix Version/s: 1.11.0
• Component/s: Core Framework
• Assignee: Mark Payne
• Reporter: Rob Fellows
• Created: 13/Nov/19 22:16
• Updated: 14/Nov/19 20:39
• Resolved: 14/Nov/19 20:39

Description

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.

 

 

Issue Links

• links to: GitHub Pull Request #3889