[
https://issues.apache.org/jira/browse/KAFKA-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972724#comment-14972724
]
Ewen Cheslack-Postava commented on KAFKA-2644:
----------------------------------------------
It shouldn't be any different. Generally, ducktape just splits getting a new
service running into installing it (which can be done via the scripts we use
for Vagrant provisioning) and running it as a Service (just requires writing a
new Service class for Kerberos, which might need to be a little more flexible
than what [~sriharsha] has, but not significantly more complex).
Given that there are already scripts for setting up Kerberos, both are probably
about the same level of effort to get working.
> Run relevant ducktape tests with SASL_PLAINTEXT and SASL_SSL
> ------------------------------------------------------------
>
> Key: KAFKA-2644
> URL: https://issues.apache.org/jira/browse/KAFKA-2644
> Project: Kafka
> Issue Type: Sub-task
> Components: security
> Reporter: Ismael Juma
> Assignee: Rajini Sivaram
> Priority: Critical
> Fix For: 0.9.0.0
>
>
> We need to define which of the existing ducktape tests are relevant. cc
> [~rsivaram]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
