zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andor Molnar (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (ZOOKEEPER-3482) SASL (Kerberos) Authentication with SSL for clients and Quorum
Date Wed, 22 Jan 2020 10:11:00 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Andor Molnar resolved ZOOKEEPER-3482.
    Fix Version/s: 3.7.0
       Resolution: Fixed

Issue resolved by pull request 1205

> SASL (Kerberos) Authentication with SSL for clients and Quorum
> --------------------------------------------------------------
>                 Key: ZOOKEEPER-3482
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3482
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.5.5
>            Reporter: Jörn Franke
>            Assignee: Mate Szalay-Beko
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.6.0, 3.5.7, 3.7.0
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
> It seems that Kerberos authentication does not work for encrypted connections of clients
and quorum. It seems that only X509 Authentication works.
> What I would have expected:
> ClientSecurePort is defined
> A keystore and truststore are deployed on the ZooKeeper servers
> Only a truststore is deployed with the client (to validate the CA of the server certificate)
> Client can authenticate with SASL (Kerberos)
> Similarly, it should work for the Quorum SSL connection.
> Is there a way to configure this in ZooKeeper?
> Note: Kerberos Authentication for SSL encrypted connection should be used instead of
X509 authentication for this case and not in addition. However, if it only works in 3.5.5
in addition then I would be interested and willing to test it.

This message was sent by Atlassian Jira

View raw message