[
https://issues.apache.org/jira/browse/NIFI-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341877#comment-15341877
]
ASF GitHub Bot commented on NIFI-1769:
--------------------------------------
Github user miquillo commented on the issue:
https://github.com/apache/nifi/pull/362
@jvwing Thanks for picking this up!
- I would 100% apply this to the AbstractS3processor. By the time I figured
it myself, I already had implemented it (in the wrong class). Should be easy to
move to the AbstractS3processor, not much code is affected by this PR.
- Definitely make this a combobox / selectable option. It was just a quick
fix to us to make it a true/false flag as we are only using Signature v4.
Indeed makes it futureproof.
- I am completely unaware of the ClientConfiguration::setSignerOverride()
and I do also dislike the system.setproperty(..). If it works the same way;
definitely go for it.
> Add support for SSE-KMS and S3 Signature Version 4 Authentication AWS
> ---------------------------------------------------------------------
>
> Key: NIFI-1769
> URL: https://issues.apache.org/jira/browse/NIFI-1769
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 0.5.1
> Reporter: Michiel Moonen
> Priority: Minor
> Labels: newbie, patch, security
> Fix For: 1.0.0
>
>
> Currently there is no support for SSE-KMS S3 Signature Version 4
> Authentication. This is necessary for enhanced security features
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
