[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279147#comment-13279147
 ] 

Antonio commented on ZOOKEEPER-1437:
------------------------------------

Hi Eugene,

It's actually happening only on a linux machine. For some reasons doesn't 
happen on windows. But I got the impression that it's related to how fast the 
process goes. Perhaps a race condition somewhere?

(The path is in windows style because I've generated the diff from an eclipse 
running on windows)


 The sasl setup is the one shown on 
https://cwiki.apache.org/ZOOKEEPER/zookeeper-and-sasl.html

{code:none}
Server {
       org.apache.zookeeper.server.auth.DigestLoginModule required
       user_super="adminsecret" 
       user_bob="bobsecret";
};

Client {
       org.apache.zookeeper.server.auth.DigestLoginModule required
       username="bob"
       password="bobsecret";
};
{code}

The authentication usually works. this issue happens only if I kill the server 
and restart it again and not all the time.

What about that "empty data[] as server response"? is it what for?


Thanks
Antonio
                
> Client uses session before SASL authentication complete
> -------------------------------------------------------
>
>                 Key: ZOOKEEPER-1437
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1437
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: java client
>    Affects Versions: 3.4.3
>            Reporter: Thomas Weise
>            Assignee: Eugene Koontz
>             Fix For: 3.4.4, 3.5.0
>
>         Attachments: ZOOKEEPER-1437.patch, ZOOKEEPER-1437.patch, 
> ZOOKEEPER-1437.patch, ZOOKEEPER-1437.patch, ZOOKEEPER-1437.patch, 
> ZOOKEEPER-1437.patch, ZOOKEEPER-1437.patch, ZOOKEEPER-1437.patch, 
> ZOOKEEPER-1437.patch
>
>
> Found issue in the context of hbase region server startup, but can be 
> reproduced w/ zkCli alone.
> getData may occur prior to SaslAuthenticated and fail with NoAuth. This is 
> not expected behavior when the client is configured to use SASL.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to