zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rammohan ganapavarapu <rammohanga...@gmail.com>
Subject Re: Observer properties for SASL authentication in 3.4.13 version
Date Mon, 24 Sep 2018 20:08:16 GMT
Ok, thanks

On Mon, Sep 24, 2018 at 11:29 AM Norbert Kalmar
<nkalmar@cloudera.com.invalid> wrote:

> Unfortunately I'm not entirely sure on this one, and I can't test it out
> right now, but shouldn't be any different then a normal follower. So you
> should configure SASL the same way. The only difference basically is that
> they are non-voters. Everything else works the same. Clients connect and
> can send read / write commands. So it would be a huge security hole if an
> observer is not configured as well.
>
> Regards,
> Norbert
>
> On Mon, Sep 24, 2018 at 10:59 AM rammohan ganapavarapu <
> rammohanganap@gmail.com> wrote:
>
> > Any thoughts?
> >
> > On Sun, Sep 23, 2018 at 8:00 PM rammohan ganapavarapu <
> > rammohanganap@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > Do we need to configure any thing on observer nodes for SASL
> > > authentication?
> > >
> > > tcpKeepAlive=true ( this is not for sasl but just asking )
> > >
> > > quorum.auth.enableSasl=true
> > > quorum.auth.learnerRequireSasl=true
> > > quorum.auth.serverRequireSasl=true
> > >
> > > What will happen if i set these properties on observers nodes as well ?
> > >
> > > Thanks,
> > > Ram
> > >
> >
>

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