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

Larry McCay commented on HADOOP-12804:
--------------------------------------

[~ste...@apache.org] - I assume that "Line 357: rethrow IOE to include 
toString() value of caught exception —so it doesn't get lost from logs." is 
supposed to be 367 in S3AFileSystem.java on branch-2 - correct?

> 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-12804-003.patch, 
> HADOOP-12804-branch-2-002.patch, HADOOP-12804-branch-2-003.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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to