You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Da Zhou (JIRA)" <ji...@apache.org> on 2018/09/05 00:25:00 UTC

[jira] [Comment Edited] (HADOOP-15694) ABFS: Allow OAuth credentials to not be tied to accounts

    [ https://issues.apache.org/jira/browse/HADOOP-15694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16603765#comment-16603765 ] 

Da Zhou edited comment on HADOOP-15694 at 9/5/18 12:24 AM:
-----------------------------------------------------------

Thank you [~mackrorysd] for adding this. The patch looks good, although there is conflict with current code base, the changes makes sense to me.
Could you also update the ABFS configuration keys in "testing_azure.md" related to this change?


was (Author: danielzhou):
Thank you [~mackrorysd] for adding this. The patch looks good, although there is conflict with current code base, but the changes makes sense to me.
Could you also update the ABFS configuration keys in "testing_azure.md" related to this change?

> 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
>
>
> 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 uses.
> 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
(v7.6.3#76005)

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