Sorry, that is a typo. It should be rest.ssl.client.auth and it should correspond to the ssl.client.auth option in the broker.
The rest.ssl.client.auth option would support values of required, requested and none (none being the default). It will control whether: * the connecting client is required to do SSL/TLS client authentication (required) * the connecting client can decide to skip the SSL/TLS client authentication (requested) * the SSL/TLS authentication is be completely disabled (none). I updated the KIP page. Thanks for noticing it. Regards Jakub On Mon, Oct 9, 2017 at 5:52 PM, Ted Yu <yuzhih...@gmail.com> wrote: > For rest.ssl.clientAuth , I don't find counterpart in existing code. Can > you add explanation on the KIP ? > > Thanks > > On Mon, Oct 9, 2017 at 8:25 AM, Jakub Scholz <ja...@scholz.cz> wrote: > > > Hi, > > > > I would like to start a discussion about KIP-208: Add SSL support to > Kafka > > Connect REST interface ( > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > > 208%3A+Add+SSL+support+to+Kafka+Connect+REST+interface > > ). > > > > I think this would be useful feature to improve the security of Kafka > > Connect. > > > > Thanks & Regards > > Jakub > > >
