Zookeeper ACL creation using SASL Kerberos authorization

ZK version 3.5.6 Curator version: 4.2.0 I am able to authenticate client principal on ZK sever but it fails while setting ACL Logs on Zookeeper server side: *2020-01-14 15:05:27,177 [myid:1] - INFO [NIOWorkerThread-2:SaslServerCallbackHandler@120] - Successfully authenticated client:

Re: Zookeeper and curator SASL authentication

Thanks for the clarification. I am able to authenticate client with Zookeeper. However, when I started to set ACLs with the same client, I get error messages. This is how I am creating curator client for setting ACLs CuratorFrameworkFactory.Builder builder =

Re: Zookeeper and curator SASL authentication

The system property name is a bit misleading... this parameter is actually specifies the username used in the ZooKeeper server principal. (in your case the server principal is: zookeeper/z...@example.com) AFAIK the ZooKeeper client (after authenticated as zkclient/z...@example.com in Kerberos

Re: Authorisation in Zookeeper

Il giorno lun 13 gen 2020 alle ore 11:06 shrikant kalani < shrikantkal...@gmail.com> ha scritto: > Enrico , > > Do you have some examples to show. > I am sorry, personally I don't examples, I am not a direct user of this feature. I hope others on the list can give practical examples You can