[
https://issues.apache.org/jira/browse/NIFI-12711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17945766#comment-17945766
]
Michael W Moser commented on NIFI-12711:
----------------------------------------
It appears that all dynamic sensitive properties, referencing a parameter or
not, are lost during export/import.
> Sensitive dynamic properties referencing parameters are not preserved during
> export/import
> ------------------------------------------------------------------------------------------
>
> Key: NIFI-12711
> URL: https://issues.apache.org/jira/browse/NIFI-12711
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 2.0.0-M1, 2.0.0-M2
> Reporter: Pierre Villard
> Priority: Major
>
> Consider an InvokeHTTP processor with a dynamic property set as sensitive and
> referencing a sensitive parameter:
> {code:java}
> Authorization => #{myBearer}{code}
> When exporting the flow definition, the reference to the sensitive parameter
> won't be preserved. We'll only see something like:
> {code:java}
> "Authorization":{"name":"Authorization","displayName":"Authorization","identifiesControllerService":false,"sensitive":true,"dynamic":true}
> {code}
> When importing the flow definition, the InvokeHTTP instance won't have the
> dynamic property. The processor will still be showing as valid and, depending
> on the endpoint, could be running without throwing errors even though the
> data would not be retrieved from the endpoint as the bearer would be missing.
> This is breaking flow deployment and can be hard to figure out when it
> happens.
> (this probably affects 1.x as well)
> Since the dynamic property is referencing a sensitive parameter we should
> preserve the reference when exporting the flow definition.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
