Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-15763 Über-JIRA: abfs phase II: Hadoop 3.3 features & fixes
  3. HADOOP-17053

ABFS: FS initialize fails for incompatible account-agnostic Token Provider setting

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.2.1
    • Fix Version/s: 3.3.1, 3.4.0
    • Component/s: fs/azure
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              snvijaya Sneha Vijayarajan
              Reporter:
              snvijaya Sneha Vijayarajan

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment