[
https://issues.apache.org/jira/browse/HDFS-10462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312848#comment-15312848
]
Hadoop QA commented on HDFS-10462:
----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s
{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 3s {color}
| {color:red} HDFS-10462 does not apply to trunk. Rebase required? Wrong
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12807802/HDFS-10462-002.patch |
| JIRA Issue | HDFS-10462 |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/15636/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> Authenticate to Azure Data Lake using client ID and keys
> --------------------------------------------------------
>
> Key: HDFS-10462
> URL: https://issues.apache.org/jira/browse/HDFS-10462
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> 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: [email protected]
For additional commands, e-mail: [email protected]
