zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jordan Zimmerman <jzimmer...@netflix.com>
Subject SaslAuthenticated
Date Thu, 17 May 2012 07:23:10 GMT
When using SASL authentication, waiting for SysConnected isn't enough. Clients need to wait
for SaslAuthenticated as well before calling ZK methods. Is there a way for a library such
as Curator to know that SASL is enabled so that it can know that it needs to wait for SaslAuthenticated?

I thought about duplicating the code in ZooKeeperSaslClient. i.e.

        String clientSection = System.getProperty(ZooKeeperSaslClient.LOGIN_CONTEXT_NAME_KEY,
        entries = Configuration.getConfiguration().getAppConfigurationEntry(clientSection);
If ( entries != null )
// then SASL is enabled

But this seems brittle. Is there another way?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message