hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiaowei Zhu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12104) libhdfs++: Make sure all steps in SaslProtocol end up calling AuthComplete
Date Fri, 07 Jul 2017 22:15:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-12104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078781#comment-16078781

Xiaowei Zhu commented on HDFS-12104:

+1,  the patch looks good.

> libhdfs++:  Make sure all steps in SaslProtocol end up calling AuthComplete
> ---------------------------------------------------------------------------
>                 Key: HDFS-12104
>                 URL: https://issues.apache.org/jira/browse/HDFS-12104
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs-client
>            Reporter: James Clampffer
>            Assignee: James Clampffer
>         Attachments: HDFS-12104.HDFS-8707.000.patch
> SaslProtocol provides an abstraction for stepping through the authentication challenge
and response stages in the Cyrus SASL library by chaining callbacks together (next one is
invoked when async io is done).
> To authenticate SaslProtocol::Authenticate is called, and when authentication is finished
SaslProtocol::AuthComplete is called which invokes an authentication completion callback.
 There's a couple cases where the intermediate callbacks return without calling AuthComplete
which breaks applications that take advantage of that callback.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message