[
https://issues.apache.org/jira/browse/HADOOP-15823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16645743#comment-16645743
]
Sean Mackrory commented on HADOOP-15823:
----------------------------------------
Thanks for the quick fix, [~DanielZhou]. Given the need to set up Azure
infrastructure to test this without ridiculous levels of mocking, I'm fine to
ignore Yetus' warning on the lack of tests.
I tried this out in my environment with a user-assigned managed identity that
worked before. The set up is identical to what I tried before, I believe, in
which I was successfully able to interact with the account once I had set the
client ID and tenant ID. This time I am able to get a valid-looking bearer
token, but I get 403's when using it on subsequent requests. Will need to
investigate more...
> ABFS: Stop requiring client ID and tenant ID for MSI
> ----------------------------------------------------
>
> Key: HADOOP-15823
> URL: https://issues.apache.org/jira/browse/HADOOP-15823
> Project: Hadoop Common
> Issue Type: Sub-task
> Affects Versions: 3.2.0
> Reporter: Sean Mackrory
> Assignee: Da Zhou
> Priority: Major
> Attachments: HADOOP-15823-001.patch
>
>
> ABFS requires the user to configure the tenant ID and client ID. From my
> understanding of MSI, that shouldn't be necessary and is an added requirement
> compared to MSI in ADLS. Can that be dropped?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
