[
https://issues.apache.org/jira/browse/HDFS-12104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410469#comment-16410469
]
Hudson commented on HDFS-12104:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13869 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/13869/])
HDFS-12104: libhdfs++: Make sure all steps in SaslProtocol end up
(james.clampffer: rev e64ba87486b9cb40474dfe27cf735cf179cb174c)
* (edit)
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/rpc/sasl_protocol.cc
> 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
> Priority: Major
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
