[
https://issues.apache.org/jira/browse/NIFI-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Batts updated NIFI-4820:
-------------------------------
Description: 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. (was: NIFI-3528 added dynamic JAAS support, but was
made specifically for Kerberos. Both SASL/SCRUM (KAFKA-3751), SASL/PLAINTEXT
(KAFKA-2658), 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.)
> 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
> Priority: Major
> Labels: kafka
>
> 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
(v7.6.3#76005)
