[
https://issues.apache.org/jira/browse/NIFI-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570971#comment-17570971
]
ASF subversion and git services commented on NIFI-10261:
--------------------------------------------------------
Commit 92750c2746924c0f31377787ffcffe619b6c41e7 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=92750c2746 ]
NIFI-10261: Ensure that when comparing Sensitive Parameters during flow sync we
decrypt values for the comparison
This closes #6231
Signed-off-by: David Handermann <[email protected]>
> When comparing local flow to cluster, all sensitive parameters are detected
> as changed
> --------------------------------------------------------------------------------------
>
> Key: NIFI-10261
> URL: https://issues.apache.org/jira/browse/NIFI-10261
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.17.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Whenever a NiFi instance syncs its flow with the cluster flow, it detects any
> differences between the flows and then uses this to determine which
> components must be stopped/disabled in order to apply updates.
> However, the StandardFlowComparator does not decrypt values before comparing
> them. Since the encryption algorithm used will produce a different value each
> time, the encrypted values cannot be simply compared to one another. They
> must be decrypted first.
> As a result, any Processor or Controller Service that references a sensitive
> parameter will be stopped/disabled each time that NiFi is synchronized to a
> cluster flow.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
