[
https://issues.apache.org/jira/browse/HADOOP-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sneha Vijayarajan updated HADOOP-17053:
---------------------------------------
Status: Patch Available (was: Open)
> ABFS: FS initialize fails for incompatible account-agnostic Token Provider
> setting
> -----------------------------------------------------------------------------------
>
> Key: HADOOP-17053
> URL: https://issues.apache.org/jira/browse/HADOOP-17053
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.2.1
> Reporter: Sneha Vijayarajan
> Assignee: Sneha Vijayarajan
> Priority: Major
> Fix For: 3.4.0
>
>
> When AuthType and Auth token provider configs are set for both generic and
> account specific config, as below:
> // account agnostic
> fs.azure.account.auth.type=CUSTOM
> fs.azure.account.oauth.provider.type=ClassExtendingCustomTokenProviderAdapter
> // account specific
> fs.azure.account.auth.type.account_name=OAuth
> fs.azure.account.oauth.provider.type.account_name=ClassExtendingAccessTokenProvider
> For account_name, OAuth with provider as ClassExtendingAccessTokenProvider
> is expected to be in effect.
> When the token provider class is being read from the config, account agnostic
> config setting is read first in the assumption that it can serve as default
> if account-specific config setting is absent. But this logic leads to failure
> when AuthType set for account specific and otherwise are different as the
> Interface implementing the token provider is different for various Auth
> Types. This leads to a Runtime exception when trying to create the oAuth
> access token provider.
> This Jira is to track the fix for it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
