[
https://issues.apache.org/jira/browse/NIFI-12736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-12736:
------------------------------------
Fix Version/s: 2.0.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Fix migration of credential properties in AWS processors
> --------------------------------------------------------
>
> Key: NIFI-12736
> URL: https://issues.apache.org/jira/browse/NIFI-12736
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.0.0-M2
> Reporter: Peter Turcsanyi
> Assignee: Peter Turcsanyi
> Priority: Minor
> Fix For: 2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In AWS processors the processor level credential properties were removed in
> 2.0 in favour of AWS Credentials Provider Service. Migration code was added
> in NIFI-12220.
> The 1.x processors allowed to configure both the processor level Access Key
> ID + Secret Access Key and AWS Credentials Provider Service properties
> ({{{}customValidate(){}}} did not check it for some reason). In this case the
> controller service took precedence.
> The migration process first checks if Access Key ID + Secret Access Key are
> configured and if they are, it creates a new controller service even if there
> was another one already in use (and the new may have outdated migrated
> credential values as the pre-existing service was used effectively in the
> flow).
> Modify the migration logic to avoid controller service duplication and to use
> the existing service.
> Also modify the default credential to
> [anonymous|https://github.com/apache/nifi/blob/ce56117e43c7cdce37ca76d54550a2b45acb508a/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-abstract-processors/src/main/java/org/apache/nifi/processors/aws/AbstractAWSProcessor.java#L415]
> as it was used if no properties were configured at all.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
