[
https://issues.apache.org/jira/browse/HADOOP-14833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-14833:
------------------------------------
Description:
Remove the s3a://user:secret@host auth mechanism from S3a.
As well as being insecure, it causes problems with S3Guard's URI matching code.
Proposed: cull it utterly. We've been telling people to stop using it since
HADOOP-3733
was:
Remove the s3a://user:secret@host auth mechanism from S3a
I think we could consider retain it as an explicit credential provider you can
ask for, so that people who cannot move off it (yet) can reconfigure their
system, but unless you do that, it stops working.
We could add a dummy credential handler which recognises the user:secret
pattern & then tells the user "no longer supported, sorry, here's how to
migrate", & add that to the default chain after everything else.
> Remove s3a user:secret authentication
> -------------------------------------
>
> Key: HADOOP-14833
> URL: https://issues.apache.org/jira/browse/HADOOP-14833
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.0.0-beta1
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Blocker
> Attachments: HADOOP-14833-001.patch
>
>
> Remove the s3a://user:secret@host auth mechanism from S3a.
> As well as being insecure, it causes problems with S3Guard's URI matching
> code.
> Proposed: cull it utterly. We've been telling people to stop using it since
> HADOOP-3733
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
