hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-14833) Remove s3a user:secret authentication
Date Tue, 28 Aug 2018 21:31:00 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-14833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Steve Loughran updated HADOOP-14833:
------------------------------------
    Target Version/s: 3.2.0  (was: 3.3.0)

> 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
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message