[
https://issues.apache.org/jira/browse/HADOOP-12537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289037#comment-15289037
]
Steve Loughran commented on HADOOP-12537:
-----------------------------------------
I'm marking this as a dependency of HADOOP-12723, which will allow any named
provider to be loaded on the classpath.
This will then allow STS to be supported if the relevant JAR is on the CP, and
a (to be written) credential provider does the binding.
Would you be able to move this patch to work with that...a whole new provider
which took the proposed config option and set things up. The new JAR dependency
would be declared "provided", so it'd be there for build and test, but not
required downstream unless the feature was required
> 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
> Priority: Minor
> Attachments: HADOOP-12537.001.patch, HADOOP-12537.002.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: [email protected]
For additional commands, e-mail: [email protected]
