It sounds like you're not setting the correct ACL in your Curator use. Curator supports ACLs.
FYI - this issue might be better to post at https://github.com/Netflix/curator/issues (a Curator mailing list is coming soon). -JZ On 4/13/12 5:14 AM, "antoniom" <[email protected]> wrote: >Hi there, > >First congrats for the great work you are doing with Zookeeper guys. >Not sure if this is the correct address to place my question. Please let >me >know if it's the wrong one. > >I was wondering if someone is aware of any issue trying to use Curator >against a Zookeeper Server that is set to use SASL. > >I have a zookeeper server with: > >"-Djava.security.auth.login.config=C:\apps\zookeeper-3.4.3\jaas.conf" >and >authProvider.1=org.apache.zookeeper.server.auth.SASLAuthenticationProvider >and using the zkClient.sh everything works fine. > >When I try to do any operation using a Curator client I always get a >KeeperErrorCode = AuthFailed for /path > >no matter if I pass >System.setProperty("java.security.auth.login.config","C:\\path\\to\\jaas.c >onf"); >before setting the Curator client. > >I'm using zookeeper 3.4.3 and Curator 1.1.5 (but I've tried with ZK 3.4.2 >as >well) > > >Thanks >Antonio > >-- >View this message in context: >http://zookeeper-user.578899.n2.nabble.com/Zookeeper-SASL-Vs-Curator-tp746 >2515p7462515.html >Sent from the zookeeper-user mailing list archive at Nabble.com. >
