[
https://issues.apache.org/jira/browse/HDFS-10685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410457#comment-16410457
]
Hudson commented on HDFS-10685:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13869 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/13869/])
HDFS-10685: libhdfs++: return explicit error when non-secured client
(james.clampffer: rev 58de2df8606cd598b41785c0c5c6bf98d66ebc15)
* (edit)
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/rpc/cyrus_sasl_engine.cc
* (edit)
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/include/hdfspp/status.h
* (edit)
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/common/status.cc
* (edit)
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/rpc/rpc_connection.cc
> libhdfs++: return explicit error when non-secured client connects to secured
> server
> -----------------------------------------------------------------------------------
>
> Key: HDFS-10685
> URL: https://issues.apache.org/jira/browse/HDFS-10685
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Reporter: Bob Hansen
> Assignee: Kai Jiang
> Priority: Major
> Attachments: HDFS-10685.HDFS-8707.000.patch,
> HDFS-10685.HDFS-8707.001.patch
>
>
> When a non-secured client tries to connect to a secured server, the first
> indication is an error from RpcConnection::HandleRpcRespose complaining about
> "RPC response with Unknown call id -33".
> We should insert code in HandleRpcResponse to detect if the unknown call id
> == RpcEngine::kCallIdSasl and return an informative error that you have an
> unsecured client connecting to a secured server.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
