[
https://issues.apache.org/jira/browse/HDFS-10685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15723471#comment-15723471
]
James Clampffer commented on HDFS-10685:
----------------------------------------
Hey [~vectorijk], sorry I didn't see this for so long. The patch you posted
looks good, the only thing I'd change is use Status::AuthenticationFailed
rather than the more general Status::Error so calling applications can handle
errors without having to compare strings. If you're still interested in
working on this you can just drop a new patch in as a comment and I'll post it
to get CI to run. Once it gets a passing run I'll commit.
> 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 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
