I managed to create ACL with authenticated client principal using below
lines of code in client:
curator
.create().creatingParentContainersIfNeeded().withACL(ZooDefs.Ids.
CREATOR_ALL_ACL).forPath("/mynode");
ZooDefs.Ids.CREATOR_ALL_ACL gives permissions to the client which is
authent
Yes, they are system properties
You can take this guide (about Kafka) as example
https://docs.confluent.io/current/kafka/authentication_sasl/authentication_sasl_gssapi.html
Il giorno 15/01/20, 13:17 "Arpit Jain" ha scritto:
I have not passed those parameters. Is this something I need to
I have not passed those parameters. Is this something I need to set in
Zookeeper (zoo.cfg) ?
On Wed, Jan 15, 2020 at 12:12 PM Enrico Olivelli - Diennea <
enrico.olive...@diennea.com> wrote:
> Usually with SASL auth you are using:
> kerberos.removeHostFromPrincipal=true
> kerberos.removeRealmFromP
Usually with SASL auth you are using:
kerberos.removeHostFromPrincipal=true
kerberos.removeRealmFromPrincipal=true
is this the case for you ?
Enrico
Il giorno 15/01/20, 13:01 "Arpit Jain" ha scritto:
I have asked in Curator mailing list as well but not much help. I am able
to set ACL
I have asked in Curator mailing list as well but not much help. I am able
to set ACL with sasl scheme by using zkCli.sh client in Zookeeper server.
The idea is to use Curator to set the ACLs so that only my client
application can access its Znodes.
On Wed, Jan 15, 2020 at 9:21 AM Szalay-Bekő Máté
I am not sure what is wrong with the code... I am not familiar with
Curator. I can try to google / reproduce this and see what is wrong, but it
will take a while for me. So first I would ask the others, maybe there is
someone who knows both ZooKeeper SASL and Curator and can help you more in
this m
