[
https://issues.apache.org/jira/browse/HADOOP-12851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173020#comment-15173020
]
Larry McCay commented on HADOOP-12851:
--------------------------------------
Ahhh - that makes sense - yeah we can use the modified config for the
provisioning - it just grabs the first provider in the path and adds the
credentials to it. So, it appears to think that it is adding it to the phoney
jceks://s3a/foobar provider which is then removed from the config from the
later getPassword integration.
The fact that it seems to be adding the creds to the jceks://s3a/foobar
provider, it seems that it is being removed from the getPassword in order to
access the s3a filesystem too.
For clarity, I will add another version though which adds it to the one with
the providerPath that doesn't include s3a based provider.
> S3AFileSystem Uptake of ProviderUtils.excludeIncompatibleCredentialProviders
> ----------------------------------------------------------------------------
>
> Key: HADOOP-12851
> URL: https://issues.apache.org/jira/browse/HADOOP-12851
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Reporter: Larry McCay
> Assignee: Larry McCay
> Attachments: HADOOP-12851-001.patch, HADOOP-12851-002.patch,
> HADOOP-12851-003.patch
>
>
> HADOOP-12846 introduced the ability for FileSystem based integration points
> of credential providers to eliminate the threat of a recursive infinite loop
> due to a provider in the same filesystem being configured.
> It was WASB has already uptaken its use in HADOOP-12846 and this patch will
> add it to the S3A integration point as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
