[
https://issues.apache.org/jira/browse/HADOOP-16068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764982#comment-16764982
]
Steve Loughran commented on HADOOP-16068:
-----------------------------------------
HADOOP-16068 patch 004
* custom oath provider can declare a UA field which is then used in the ABFS
client UA header (for audit logs when the login credentials have a more complex
provenance)
* fix for HADOOP-16103 (more UGI resets)
* testing: Azure Amsterdam; found HADOOP-16103. more resetUGIs *seems* to fix
this
* not done: tests to verify that the classic lifecycle works. The stub class
for testing is there.
I'm going to do another iteration here and pause. I think the code is OK, but
it is hitting the limits of testability —primarily because the extension points
for DT issuing rely on kerberos being running, which confuses other tests.
# need some DT lifecycle tests which verify that the "classic" lifecycle still
works;
# To test the login extension point, without doing a full HADOOP-14556-style
token marshalling plugin, this will need a proxy to the standard OAuth login.
> ABFS Auth and DT plugins to be bound to specific URI of the FS
> --------------------------------------------------------------
>
> Key: HADOOP-16068
> URL: https://issues.apache.org/jira/browse/HADOOP-16068
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.2.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Attachments: HADOOP-16068-001.patch, HADOOP-16068-002.patch,
> HADOOP-16068-003.patch, HADOOP-16068-004.patch
>
>
> followup from HADOOP-15692: pass in the URI & conf of the owner FS to bind
> the plugins to the specific FS instance. Without that you can't have per FS
> auth
> +add a stub DT plugin for testing, verify that DTs are collected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
