[jira] [Commented] (HADOOP-12804) Read Proxy Password from Credential Providers in S3 FileSystem

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-12804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322241#comment-15322241 ] 

Hadoop QA commented on HADOOP-12804:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  5s{color} | {color:red} HADOOP-12804 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12794416/HADOOP-12804-001.patch |
| JIRA Issue | HADOOP-12804 |
| Console output | https://builds.apache.org/job/PreCommit-HADOOP-Build/9701/console |
| Powered by | Apache Yetus 0.4.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org