Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
From: EronWright <git@git.apache.org>
To: issues@flink.incubator.apache.org
Reply-To: issues@flink.incubator.apache.org
References: <git-pr-3600-flink@git.apache.org>
In-Reply-To: <git-pr-3600-flink@git.apache.org>
Subject: [GitHub] flink issue #3600: [FLINK-6117]Make setting of 'zookeeper.sasl.disable' work...
Content-Type: text/plain
Message-Id: <20170324162806.0C32DDFF0F@git1-us-west.apache.org>
Date: Fri, 24 Mar 2017 16:28:06 +0000 (UTC)
archived-at: Fri, 24 Mar 2017 16:28:11 -0000

Github user EronWright commented on the issue:

    https://github.com/apache/flink/pull/3600
  
    To recap, when the ZK server is configured to use SASL, the client is challenged accordingly.  The client checks for a login entry in the JAAS config to obtain a kerberos credential, and issues a warning if one isn't found.  SASL may be explicitly disabled on the client using the system property `zookeeper.sasl.clientconfig`.   
    
    Flink provides a configuration setting with which to disable SASL on the client, which causes the system property to be set.     _I cannot think of why the default value would be 'true'._   The behavior of 1.2.0 is that the default is 'false' (because it effectively wasn't implemented).   Maybe the default should remain 'false'?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---