You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/09/05 08:52:00 UTC

[jira] [Created] (HADOOP-14833) Move s3a user:secret auth out of the main chain of auth mechanisms

Steve Loughran created HADOOP-14833:
---------------------------------------

             Summary: Move s3a user:secret auth out of the main chain of auth mechanisms
                 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
            Priority: Minor


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
(v6.4.14#64029)

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