You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Wellington Chevreuil (Jira)" <ji...@apache.org> on 2020/06/19 10:02:00 UTC

[jira] [Updated] (HBASE-24579) Failed SASL authentication does not result in an exception on client side

     [ https://issues.apache.org/jira/browse/HBASE-24579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wellington Chevreuil updated HBASE-24579:
-----------------------------------------
    Affects Version/s: 2.4.0
                       2.3.0
                       3.0.0-alpha-1
                       2.2.5

> Failed SASL authentication does not result in an exception on client side
> -------------------------------------------------------------------------
>
>                 Key: HBASE-24579
>                 URL: https://issues.apache.org/jira/browse/HBASE-24579
>             Project: HBase
>          Issue Type: Bug
>          Components: rpc
>    Affects Versions: 3.0.0-alpha-1, 2.3.0, 2.4.0, 2.2.5
>            Reporter: Szabolcs Bukros
>            Assignee: Szabolcs Bukros
>            Priority: Major
>
> When HBaseSaslRpcClient.saslConnect tries to authenticate it only reads the input stream if the process is not complete yet. However if the authentication failed and the process is completed the exception sent back in the stream never gets read.
> We should always try to read the input stream even if the process is complete to make sure it was empty.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)