Todd Lipcon created ZOOKEEPER-1510:
--------------------------------------
Summary: Should not log SASL errors for non-secure usage
Key: ZOOKEEPER-1510
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1510
Project: ZooKeeper
Issue Type: Improvement
Components: java client
Affects Versions: 3.4.3
Reporter: Todd Lipcon
Priority: Minor
Since SASL support was added, all connections with non-secure clients have
started logging messages like:
2012-07-01 02:13:34,986 WARN org.apache.zookeeper.client.ZooKeeperSaslClient:
SecurityException: java.lang.SecurityException: Unable to locate a login
configuration occurred when trying to find JAAS configuration.
2012-07-01 02:13:34,986 INFO org.apache.zookeeper.client.ZooKeeperSaslClient:
Client will not SASL-authenticate because the default JAAS configuration
section 'Client' could not be found. If you are not using SASL, you may ignore
this. On the other hand, if you expected SASL to work, please fix your JAAS
configuration.
Despite the "you may ignore this" qualifier, I've seen a lot of users confused
by this message. Instead, it would be better to either log at DEBUG level, or
piggy back the SASL information onto the "Opening socket connection" message
(eg "Opening socket connection to X:2181. Will not use SASL because no
configuration was located.")
--
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
