[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016984#comment-17016984
 ] 

Mate Szalay-Beko commented on ZOOKEEPER-3482:
---------------------------------------------

I updated my two PRs. I think, this bug report can be closed (after the PRs got 
merged).

In the PRs I added new unit tests and updated the ZooKeeper Admin Guide, and 
ZooKeeper Programming Guide (these are stored in git). 
I also updated the wiki here: 
https://cwiki.apache.org/confluence/display/ZOOKEEPER/Client-Server+mutual+authentication
Together with [~andor] we also tested Kerberos authentication over SSL on real 
Hadoop clusters, so I am confident to say that both features are working at 
least on 3.5.5, 3.5.6 and on the current 3.6 and master branches.

I know that there is an other requirement in this Jira, namely: allowing client 
SSL for ZooKeeper without actual authentication (no keystore in client side, 
only truststore). This is not working now in ZooKeeper, but I don't think it 
would be a bug... this is simply how the SSL feature was designed originally. 
(In ZooKeeper SSL was plugged in as an authentication module.) Although I think 
it is a good idea and we should implement it.  We should issue a separate Jira 
for this. I would be happy to work on this, but not sure when I will have time 
exactly.

> 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
>          Time Spent: 1h 10m
>  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
(v8.3.4#803005)

Reply via email to