[
https://issues.apache.org/jira/browse/NIFI-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16952178#comment-16952178
]
ASF subversion and git services commented on NIFI-4820:
-------------------------------------------------------
Commit d570fe81543b706acf9a797fb05fac68a384b3f4 in nifi's branch
refs/heads/master from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d570fe8 ]
NIFI-4820 This closes #3813. Improving security configuration for Kafka 2.0
processors
Signed-off-by: Joe Witt <[email protected]>
> Extend dynamic JAAS support for Kafka processors
> ------------------------------------------------
>
> Key: NIFI-4820
> URL: https://issues.apache.org/jira/browse/NIFI-4820
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.4.0, 1.5.0, 1.6.0
> Reporter: Robert Batts
> Assignee: Bryan Bende
> Priority: Major
> Labels: kafka
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> NIFI-3528 added dynamic JAAS support, but was made specifically for Kerberos.
> Both SASL/SCRUM (KAFKA-3751), SASL/PLAINTEXT (KAFKA-2658 / KAFKA-3149), and
> any future Kafka SASL mechanism should have the ability to have a dynamic
> JAAS as well since they are implemented in Kafka. I would imagine this would
> come in the form of a Service for re-usability, but a less attractive option
> (in terms of Nifi security) may be to allow users to set sasl.jaas.config
> directly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
