[
https://issues.apache.org/jira/browse/NIFI-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742039#comment-17742039
]
Dirk Hennig commented on NIFI-11763:
------------------------------------
Hello David, many thanks for your feedback. I can appreciate that you take
security serious!
In my use case I do not access any sensitive information and we do have only
authorized users. In my use case I concatenate a few attributes coming along
with the flow files together with a fixed part and this string is used to
lookup the information for the destination of the flow file. In one specific
case I search for sftp host name user name and permissions. This reduces the
amount of independent PutSFTP processors.
Do you see any other efficient way to achieve this?
Greetings, Dirk
> evaluateELString not evaluating ContextParameters
> -------------------------------------------------
>
> Key: NIFI-11763
> URL: https://issues.apache.org/jira/browse/NIFI-11763
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.21.0, 1.22.0
> Environment: Linux NiFi 3 nodes cluster - 8 CPU core +32 GB of RAM
> per node
> Reporter: Dirk Hennig
> Priority: Major
> Attachments: Complex_UpdateAttribute_Test.json
>
>
> When using Expression Language it was possible to lookup parameters from
> ContextParameters and variables from VariableRegistry. Examples:
> ${ literal('#\{Tenant-Testing-HOST1}'):evaluateELString() }
> ${ literal('${Testvar}'):evaluateELString() }
> Both were working in NiFi 1.18.0. Now with NiFi version 1.21.0 this stopped
> working for ContextParameters and only lookups of varaibles are working.
> Please see the attached template with an example flow.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
