[
https://issues.apache.org/jira/browse/HADOOP-12804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322245#comment-15322245
]
Steve Loughran commented on HADOOP-12804:
-----------------------------------------
Larry, can you sync this up with the current branch-2 code, do a test run, and
tell uswhich s3 infrastructure did you test against.
Here I'm curious about how proxy testing went before/after as well as direct
testing, though that won't be as easy.
Also, looking at the code: should the debug statement really be logging the
password? Print it's length, maybe —but not the value
> Read Proxy Password from Credential Providers in S3 FileSystem
> --------------------------------------------------------------
>
> Key: HADOOP-12804
> URL: https://issues.apache.org/jira/browse/HADOOP-12804
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Larry McCay
> Assignee: Larry McCay
> Priority: Minor
> Attachments: HADOOP-12804-001.patch
>
>
> HADOOP-12548 added credential provider support for the AWS credentials to
> S3FileSystem. This JIRA is for considering the use of the credential
> providers for the proxy password as well.
> Instead of adding the proxy password to the config file directly and in clear
> text, we could provision it in addition to the AWS credentials into a
> credential provider and keep it out of clear text.
> In terms of usage, it could be added to the same credential store as the AWS
> credentials or potentially to a more universally available path - since it is
> the same for everyone. This would however require multiple providers to be
> configured in the provider.path property and more open file permissions on
> the store itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
