pushpavanthar commented on a change in pull request #3360: Documentation :  
ConsumerKafka_2_0 - updated configuration details re…
URL: https://github.com/apache/nifi/pull/3360#discussion_r264813492
 
 

 ##########
 File path: 
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-2-0-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaRecord_2_0/additionalDetails.html
 ##########
 @@ -112,16 +126,59 @@ <h4>SASL_PLAINTEXT - PLAIN</h4>
       password="nifi-password";
     };
             </pre>
+        The JAAS configuration can be provided by either of below ways
+        <ol type="1">
+            <li>specify the java.security.auth.login.config system property in
+                NiFi's bootstrap.conf. This limits you to use only one user 
credential across the cluster.</li>
+            <pre>
+                
java.arg.16=-Djava.security.auth.login.config=/path/to/kafka_client_jaas.conf
+            </pre>
+            <li>add user attribute 'sasl.jaas.config' in the processor 
configurations. This method allows one to have multiple consumers with 
different user credentials or gives flexibility to consume from multiple kafka 
clusters.</li>
+            <pre>
+                sasl.jaas.config : 
org.apache.kafka.common.security.plain.PlainLoginModule required
+                                        username="nifi"
+                                        password="nifi-password";
+            </pre>
+        </ol>
         </p>
         <p>
             <b>NOTE:</b> It is not recommended to use a SASL mechanism of 
PLAIN with SASL_PLAINTEXT, as it would transmit
             the username and password unencrypted.
+            <b>NOTE:</b> The Kerberos Service Name is not required for SASL 
mechanism of PLAIN. However, processor warns saying this attribute has to be 
filled with non empty string. You can choose to fill any random string. I 
prefer "null".
 
 Review comment:
   Updated latest commit as suggested.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to