From ffbd05b3313ae60a0211062c48374961fbd9b741 Mon Sep 17 00:00:00 2001
From: Anushree Ringne <54858723+anusricorp@users.noreply.github.com>
Date: Tue, 27 Oct 2020 11:48:41 -0700
Subject: [PATCH] Added step to give access to user get kerb ticket

---
 DomainJoined-Producer-Consumer/README.md | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/DomainJoined-Producer-Consumer/README.md b/DomainJoined-Producer-Consumer/README.md
index 8c12552..107c9d3 100644
--- a/DomainJoined-Producer-Consumer/README.md
+++ b/DomainJoined-Producer-Consumer/README.md
@@ -147,12 +147,17 @@ This conversation was marked as resolved by anusricorp
 
     > [!Note]  
     > This command requires Ambari access. If your cluster is behind an NSG, run this command from a machine that can access Ambari.
+1. First give access to users in the Ranger policies. https://docs.microsoft.com/en-us/azure/hdinsight/domain-joined/apache-domain-joined-run-kafka
+Then for the user, get a kerberos ticket with the command. Enter the password when it prompts for it. 
+
+    ```bash
+    kinit <username>
+    ```
 1. Create Kafka topic, `myTest`, by entering the following command:
 
     ```bash
     java -jar -Djava.security.auth.login.config=/usr/hdp/current/kafka-broker/config/kafka_client_jaas.conf kafka-producer-consumer.jar create myTest $KAFKABROKERS
     ```
-
 1. To run the producer and write data to the topic, use the following command:
 
     ```bash