Matteo Bertozzi created ZOOKEEPER-1497:
------------------------------------------
Summary: Allow SASL login with JAAS configuration to be
programmatically set (rather than only by reading JAAS configuration file)
Key: ZOOKEEPER-1497
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1497
Project: ZooKeeper
Issue Type: Improvement
Components: server
Affects Versions: 3.3.5, 3.4.3
Reporter: Matteo Bertozzi
Currently the CnxnFactory checks for "java.security.auth.login.config" to
decide whether or not enable SASL.
* zookeeper/server/NIOServerCnxnFactory.java
* zookeeper/server/NettyServerCnxnFactory.java
** configure() checks for "java.security.auth.login.config"
*** If present start the new Login("Server", SaslServerCallbackHandler(conf))
But since the SaslServerCallbackHandler does the right thing just checking if
getAppConfigurationEntry() is empty, we can allow SASL with JAAS configuration
to be programmatically just checking weather or not a configuration entry is
present instead of "java.security.auth.login.config".
(Something quite similar was done for the SaslClient in ZOOKEEPER-1373)
--
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
