[
https://issues.apache.org/jira/browse/KAFKA-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3166:
-------------------------------
Resolution: Fixed
Reviewer: sriharsha chintalapani (was: Jun Rao)
Fix Version/s: 0.9.0.1
Status: Resolved (was: Patch Available)
> 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
> Fix For: 0.9.0.1
>
>
> 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)
