From issues-return-2177-archive-asf-public=cust-asf.ponee.io@zookeeper.apache.org Tue Jan 7 15:19:02 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 8DE00180643 for ; Tue, 7 Jan 2020 16:19:02 +0100 (CET) Received: (qmail 34162 invoked by uid 500); 7 Jan 2020 15:19:02 -0000 Mailing-List: contact issues-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zookeeper.apache.org Delivered-To: mailing list issues@zookeeper.apache.org Received: (qmail 34146 invoked by uid 99); 7 Jan 2020 15:19:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jan 2020 15:19:01 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id AC912E3065 for ; Tue, 7 Jan 2020 15:19:00 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id 25E0A780565 for ; Tue, 7 Jan 2020 15:19:00 +0000 (UTC) Date: Tue, 7 Jan 2020 15:19:00 +0000 (UTC) From: "Mate Szalay-Beko (Jira)" To: issues@zookeeper.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ZOOKEEPER-3482) SASL (Kerberos) Authentication with SSL for clients and Quorum MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ZOOKEEPER-3482?page=3Dcom.atlas= sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D= 17009816#comment-17009816 ]=20 Mate Szalay-Beko commented on ZOOKEEPER-3482: --------------------------------------------- update: I managed to create some working unit tests on the master branch. I= tested SASL Digest + SSL, and also SASL Kerberos + SSL. So it seems workin= g on the master branch (although due to some conflict, it requires more wor= k to make the tests work on the branch 3.5). the PR for the master branch: = https://github.com/apache/zookeeper/pull/1204 I want to work now on the 3.5 branch to see if the problem exists there or = not. I also want to reproduce this scenario on a real kerberized server. > 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=C3=B6rn Franke > Assignee: Mate Szalay-Beko > Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > It seems that Kerberos authentication does not work for encrypted connect= ions 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? > =C2=A0 > 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 willi= ng to test it. -- This message was sent by Atlassian Jira (v8.3.4#803005)