[
https://issues.apache.org/jira/browse/NIFI-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701343#comment-16701343
]
Koji Kawamura commented on NIFI-5842:
-------------------------------------
Hi [~kei miyauchi]
There is also a note on dynamic JAAS config in the additionalDetails:
{quote}Alternatively, starting with Apache NiFi 1.2.0 which uses the Kafka
0.10.2 client, the JAAS configuration when using GSSAPI can be provided by
specifying the Kerberos Principal and Kerberos Keytab directly in the processor
properties. This will dynamically create a JAAS configuration like above, and
will take precedence over the java.security.auth.login.config system property.
{quote}
Does the note suffice? If you have any idea to make it more clear, please let
us know. Thanks!
> AdditionalDetails of Kafka Processor0.10+ is not correct.
> ---------------------------------------------------------
>
> Key: NIFI-5842
> URL: https://issues.apache.org/jira/browse/NIFI-5842
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: kei miyauchi
> Priority: Trivial
>
> On additionalDetails of Kafka processor say:
> _> If the SASL mechanism is GSSAPI, then the client must provide a JAAS
> configuration to authenticate_
> _> If the SASL mechanism is PLAIN, then client must provide a JAAS
> configuration to authenticate_
> This is already not true because of NIFI-3528.
> Setting Principal and Keytab is enough.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
