hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Hansen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-10685) libhdfs++: return explicit error when non-secured client connects to secured server
Date Sun, 11 Sep 2016 00:20:20 GMT

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

Bob Hansen commented on HDFS-10685:

Thanks for putting that together, [~vectorijk]!

I'll have to check when I get back to the office, but I think we may have a specific Status
instance for an Authentication error which we should use in this case.  If we don't, we should
add one for this.

Since Apache has the Hadoop Jira loked down at the moment, feel free to put the patch up on
github onto a fork of https://github.com/apache/hadoop/tree/HDFS-8707.  Also, I think the
patch you posted may be reversed.  :-)

> 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
> 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

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