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-12537) s3a: Add flag for session ID to allow Amazon STS temporary credentials
Date Wed, 01 Jun 2016 18:43:59 GMT

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

Steve Loughran updated HADOOP-12537:
------------------------------------
    Attachment: HADOOP-12537-branch-2.005.patch

This patch 005; patch 004 merged in and reworked somewhat

Production:
# throwing an explicit {{CredentialInitializationException}} (backported to the other providers).
This declares itself as non-retryable, and, being an explicit type, can be looked for in names.
# Changed the exception text message.

Test
# moved the STS option flag out of the contract tests, instead adding one to the S3A tests
only.
# added a test for missing session token.
# extended the existing test with an attempt to create an FS with an invalid token.

Docs
# more detail, an example, and some test docs.

The new test —taking the newly issued session token and trying to init with a now-invalid
triple of (key-id, key-secret, sessionId) is something I'd have expected to fail. It isn't.
This is something that needs to be fixed.

Hypotheses

* I've misunderstood something
* credential setup isn't working as expected; perhaps the permanent keys are being picked
up, not these new ones.
* AWS is doing something underneath.

[~mackrorysd]: could you look at that? Once that test is passing I think we're pretty much
good to go here


> s3a: Add flag for session ID to allow Amazon STS temporary credentials
> ----------------------------------------------------------------------
>
>                 Key: HADOOP-12537
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12537
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: fs/s3
>    Affects Versions: 2.7.1
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>            Priority: Minor
>         Attachments: HADOOP-12537-branch-2.005.patch, HADOOP-12537.001.patch, HADOOP-12537.002.patch,
HADOOP-12537.003.patch, HADOOP-12537.004.patch, HADOOP-12537.diff, HADOOP-12537.diff
>
>
> Amazon STS allows you to issue temporary access key id / secret key pairs for your a
user / role. However, using these credentials also requires specifying a session ID. There
is currently no such configuration property or the required code to pass it through to the
API (at least not that I can find) in any of the S3 connectors.



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


Mime
View raw message