zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Hunt (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-1510) Should not log SASL errors for non-secure usage
Date Wed, 01 Aug 2012 19:02:02 GMT

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

Patrick Hunt updated ZOOKEEPER-1510:

    Fix Version/s: 3.5.0
> 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
>            Assignee: Todd Lipcon
>            Priority: Minor
>             Fix For: 3.4.4, 3.5.0
>         Attachments: zookeeper-1510.txt, zookeeper-1510.txt
> 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


View raw message