Uploaded image for project: 'ZooKeeper'
  1. ZooKeeper
  2. ZOOKEEPER-1512

Reduce log level of missing ZookeeperSaslClient Security Exception

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • java client
    • None

    Description

      When running the Java client you frequently get messages like the following:

      org.apache.zookeeper.client.ZooKeeperSaslClient SecurityException: java.lang.SecurityException: Unable to locate a login configuration occurred when trying to find JAAS configuration.

      In cases where we don't want this configuration enabled, the logs get spammed with this message. It's scope should lowered to debug/trace to prevent flooding logs.

      Attachments

        Issue Links

          Is contained by

          Bug - A problem which impairs or prevents the functions of the product. ZOOKEEPER-1657 Increased CPU usage by unnecessary SASL checks

          • Major - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. ZOOKEEPER-1623 Authentication using SASL

          • Major - Major loss of function.
          • Open
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. ZOOKEEPER-1510 Should not log SASL errors for non-secure usage

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              mkwhitacre Micah Whitacre
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated: