hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Mackrory (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-15694) ABFS: Allow OAuth credentials to not be tied to accounts
Date Wed, 05 Sep 2018 04:20:00 GMT

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

Sean Mackrory updated HADOOP-15694:
    Attachment: HADOOP-15694.003.patch

> ABFS: Allow OAuth credentials to not be tied to accounts
> --------------------------------------------------------
>                 Key: HADOOP-15694
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15694
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>            Priority: Major
>         Attachments: HADOOP-15694.001.patch, HADOOP-15694.002.patch, HADOOP-15694.003.patch
> Now that there's OAuth support, it's possible to have a notion of identity that's distinct
from the account itself. If a cluster is configured via OAuth with it's own identity, it's
likely operators will want to use that identity regardless of which storage account a job
> So OAuth configs right now (and probably others) are looked up with <config_key>.<account>.
I propose that we add a function for looking up these configs that returns an account-specific
value if it exists, but in the event it does not will also try to return <config_key>,
if that exists.
> I can work on a patch for this if nobody has any objections.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message