[
https://issues.apache.org/jira/browse/HDFS-17606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17874855#comment-17874855
]
ASF GitHub Bot commented on HDFS-17606:
---------------------------------------
steveloughran commented on code in PR #7005:
URL: https://github.com/apache/hadoop/pull/7005#discussion_r1721637057
##########
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocol/datatransfer/sasl/CustomizedCallbackHandler.java:
##########
@@ -34,6 +36,24 @@ public void handleCallback(List<Callback> callbacks, String
username, char[] pas
}
}
+ static CustomizedCallbackHandler delegate(Object delegated) {
Review Comment:
As of last week, DynMethod exists in hadoop common to assist here. Have look
to see if it would help or are your needs better. A key aspect is can extract
IOEs from the invocation
> Do not require implementing CustomizedCallbackHandler
> -----------------------------------------------------
>
> Key: HDFS-17606
> URL: https://issues.apache.org/jira/browse/HDFS-17606
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: security
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Major
> Labels: pull-request-available
>
> HDFS-17576 added a CustomizedCallbackHandler interface which declares the
> following method:
> {code}
> void handleCallback(List<Callback> callbacks, String name, char[] password)
> throws UnsupportedCallbackException, IOException;
> {code}
> This Jira is to allow an implementation to define the handleCallback method
> without implementing the CustomizedCallbackHandler interface. It is to avoid
> a security provider depending on the HDFS project.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
