Return-Path: X-Original-To: apmail-kafka-dev-archive@www.apache.org Delivered-To: apmail-kafka-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DE75F184AE for ; Thu, 28 Jan 2016 20:16:53 +0000 (UTC) Received: (qmail 19756 invoked by uid 500); 28 Jan 2016 20:16:40 -0000 Delivered-To: apmail-kafka-dev-archive@kafka.apache.org Received: (qmail 19601 invoked by uid 500); 28 Jan 2016 20:16:40 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 19578 invoked by uid 99); 28 Jan 2016 20:16:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jan 2016 20:16:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D90222C1F64 for ; Thu, 28 Jan 2016 20:16:39 +0000 (UTC) Date: Thu, 28 Jan 2016 20:16:39 +0000 (UTC) From: "Ismael Juma (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (KAFKA-3166) Disable SSL client authentication for SASL_SSL security protocol MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KAFKA-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3166: ---------------------------------- Assignee: Ismael Juma > Disable SSL client authentication for SASL_SSL security protocol > ---------------------------------------------------------------- > > Key: KAFKA-3166 > URL: https://issues.apache.org/jira/browse/KAFKA-3166 > Project: Kafka > Issue Type: Improvement > Components: security > Affects Versions: 0.9.0.0 > Reporter: Ismael Juma > Assignee: Ismael Juma > > A useful scenario is for a broker to require clients to authenticate either via SSL or via SASL (with SASL_SSL security protocol). With the current code, this is not possible to achieve. If we set `ssl.client.auth` to `required`, then it will be required for both SSL and SASL. > I suggest we hardcode `ssl.client.auth` to `none` for the `SASL_SSL` case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)