You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Germán Blanco (JIRA)" <ji...@apache.org> on 2013/04/11 12:51:22 UTC
[jira] [Commented] (ZOOKEEPER-1623) Authentication using SASL
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628832#comment-13628832 ]
Germán Blanco commented on ZOOKEEPER-1623:
------------------------------------------
This is the first patch that I submit and the first time that I input anything in JIRA, so I might have done silly things as sending the previous comment without intention.
My interpretation of the text in the TODO that is in the current ZooKeeperSaslClient.java, is that this modification should be done. And it solves the problem of the excessive logging.
I didn't think that a test case was really required for this, but since it is in the procedure, one is suggested in the patch.
Can anybody please tell me if the change is correct?
> Authentication using SASL
> -------------------------
>
> Key: ZOOKEEPER-1623
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1623
> Project: ZooKeeper
> Issue Type: Bug
> Affects Versions: 3.4.5
> Reporter: Christian Wuertz
> Attachments: ZOOKEEPER-1623.patch
>
>
> First of all, I'm just running some test and thus I don't wan't/need any authentication at all. So I didn't configured any. But running my Java client with an Oracle JVM (1.6.38) I run into the following problem:
> `2013-01-16 17:40:30,659 [main] INFO org.apache.zookeeper.ZooKeeper - Initiating client connection, connectString=192.168.2.28:2181 sessionTimeout=5000 watcher=master.Master@eb42cbf
> 2013-01-16 17:40:30,674 [main] DEBUG org.apache.zookeeper.ClientCnxn - zookeeper.disableAutoWatchReset is false
> 2013-01-16 17:40:30,698 [Thread-0] DEBUG master.Master - Master waits...
> 2013-01-16 17:40:30,701 [main-SendThread(Teots-PC:2181)] INFO org.apache.zookeeper.ClientCnxn - Opening socket connection to server Teots-PC/192.168.2.28:2181. Will not attempt to authenticate using SASL (Unable to locate a login configuration)
> 2013-01-16 17:40:30,706 [main-SendThread(Teots-PC:2181)] INFO org.apache.zookeeper.ClientCnxn - Socket connection established to Teots-PC/192.168.2.28:2181, initiating session
> 2013-01-16 17:40:30,708 [main-SendThread(Teots-PC:2181)] DEBUG org.apache.zookeeper.ClientCnxn - Session establishment request sent on Teots-PC/192.168.2.28:2181
> 2013-01-16 17:40:30,709 [main-SendThread(Teots-PC:2181)] DEBUG org.apache.zookeeper.client.ZooKeeperSaslClient - Could not retrieve login configuration: java.lang.SecurityException: Unable to locate a login configuration
> 2013-01-16 17:40:30,730 [main-SendThread(Teots-PC:2181)] INFO org.apache.zookeeper.ClientCnxn - Session establishment complete on server Teots-PC/192.168.2.28:2181, sessionid = 0x13c44254fd70003, negotiated timeout = 5000
> 2013-01-16 17:40:30,732 [main-EventThread] DEBUG master.Master - Master recieved an event: None
> 2013-01-16 17:40:30,732 [main-SendThread(Teots-PC:2181)] DEBUG org.apache.zookeeper.client.ZooKeeperSaslClient - Could not retrieve login configuration: java.lang.SecurityException: Unable to locate a login configuration
> 2013-01-16 17:40:30,732 [main-EventThread] DEBUG master.Master - Master's state: SyncConnected
> 2013-01-16 17:40:30,732 [main-SendThread(Teots-PC:2181)] DEBUG org.apache.zookeeper.client.ZooKeeperSaslClient - Could not retrieve login configuration: java.lang.SecurityException: Unable to locate a login configuration`
> This does not happen with an OpenJDK JVM.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira