[ https://issues.apache.org/jira/browse/KAFKA-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edoardo Comar resolved KAFKA-3679. ---------------------------------- Resolution: Won't Fix The Documentation http://kafka.apache.org/0100/documentation.html#security_sasl_plain_brokerconfig suggests to plugin a security provider and implement your own SaslServer by copy'n'paste of the provided kafka PlainSaslServer so closing as wont't fix > Allow reuse of implementation of RFC 4616 in PlainSaslServer > ------------------------------------------------------------- > > Key: KAFKA-3679 > URL: https://issues.apache.org/jira/browse/KAFKA-3679 > Project: Kafka > Issue Type: Improvement > Components: clients > Affects Versions: 0.10.0.0 > Reporter: Edoardo Comar > Assignee: Edoardo Comar > > Using SASL PLAIN in production may require a different username/password > checking than what is currently in the codebase, based on data contained in > the server jaas.conf. > To do so, a deployment needs to extend the SaslPlainServer as described here > http://kafka.apache.org/0100/documentation.html#security_sasl_plain_production > However the evaluate(byes) method still needs to impleemnt RFC4616, so it is > useful to separate the password checking from the reading of the data from > the wire. > A simple extract method into an overridable methos should suffice -- This message was sent by Atlassian JIRA (v6.3.4#6332)