[
https://issues.apache.org/jira/browse/METRON-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940945#comment-15940945
]
ASF GitHub Bot commented on METRON-797:
---------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/490
Good catch. I made the dependency explicit and created the JIRAs that I
know about for kerberos
[here](https://issues.apache.org/jira/browse/METRON-802?jql=labels%20%3D%20kerberos%20AND%20project%20%3D%20Metron)
> Pass security.protocol and enable auto-renew for the storm topologies
> ---------------------------------------------------------------------
>
> Key: METRON-797
> URL: https://issues.apache.org/jira/browse/METRON-797
> Project: Metron
> Issue Type: Improvement
> Reporter: Casey Stella
> Assignee: Casey Stella
> Labels: kerberos
>
> METRON-793 migrated the storm topologies to the storm-kafka-client spout,
> which supports kerberos. To complete the kerberos work on the existing
> topologies, we need to be able to enable the spouts and kafka writers to use
> security protocols other than PLAINTEXT. Also, enabling auto-renew plugins
> for storm will enable the topologies to run for extended durations in a
> kerberized cluster.
> NOTE: This does not encompass MPack changes to enable kerberos or fix the
> sensors to work with a kerberized kafka. That would be follow-on work.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
