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 "Chris Nauroth (JIRA)" <ji...@apache.org> on 2016/06/06 21:17:21 UTC
[jira] [Moved] (HADOOP-13242) Authenticate to Azure Data Lake using
client ID and keys
[ https://issues.apache.org/jira/browse/HADOOP-13242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Nauroth moved HDFS-10462 to HADOOP-13242:
-----------------------------------------------
Component/s: (was: hdfs-client)
fs/azure
Key: HADOOP-13242 (was: HDFS-10462)
Project: Hadoop Common (was: Hadoop HDFS)
> Authenticate to Azure Data Lake using client ID and keys
> --------------------------------------------------------
>
> Key: HADOOP-13242
> URL: https://issues.apache.org/jira/browse/HADOOP-13242
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/azure
> Environment: All
> Reporter: Atul Sikaria
> Assignee: Atul Sikaria
> Attachments: HDFS-10462-001.patch, HDFS-10462-002.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Current OAuth2 support (used by HADOOP-12666) supports getting a token using client creds. However, the client creds support does not pass the "resource" parameter required by Azure AD. This work adds support for the "resource" parameter when acquring the OAuth2 token from Azure AD, so the client credentials can be used to authenticate to Azure Data Lake.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org