[ https://issues.apache.org/jira/browse/HDFS-10685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Clampffer updated HDFS-10685: ----------------------------------- Attachment: HDFS-10685.HDFS-8707.000.patch I just took the diff posted by [~vectorijk] and turned it into a patch. A couple minor modifications: -cast callid() result to a int32_t to avoid signed to unsigned comparison warnings -Replaced Status::Errror with Status::AuthenticationFailed -Add an overload to Status::AuthenticationFailed that can take a message so it can keep the "You have a non-secured client connecting to a secured server" detail. -Change Status::Error to Status::AuthenticationFailed in cyrus_sasl_engine.cc to catch errors there as well. [~xiaowei.zhu] could you do a review please? > 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 > Attachments: HDFS-10685.HDFS-8707.000.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 (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org