You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Bryan Bende (Jira)" <ji...@apache.org> on 2019/10/14 18:52:00 UTC

[jira] [Updated] (NIFI-4820) Extend dynamic JAAS support for Kafka processors

     [ https://issues.apache.org/jira/browse/NIFI-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Bende updated NIFI-4820:
------------------------------
    Fix Version/s: 1.10.0
           Status: Patch Available  (was: In Progress)

> 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.6.0, 1.5.0, 1.4.0
>            Reporter: Robert Batts
>            Assignee: Bryan Bende
>            Priority: Major
>              Labels: kafka
>             Fix For: 1.10.0
>
>          Time Spent: 10m
>  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)