Skip to content

Commit a4efd9b

Browse files
authored
Update apache-kafka-ssl-encryption-authentication.md
1 parent 8797b61 commit a4efd9b

File tree

1 file changed

+12
-1
lines changed

1 file changed

+12
-1
lines changed

articles/hdinsight/kafka/apache-kafka-ssl-encryption-authentication.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,9 @@ This article shows you how to set up Transport Layer Security (TLS) encryption,
1414
> [!Important]
1515
> There are two clients which you can use for Kafka applications: a Java client and a console client. Only the Java client `ProducerConsumer.java` can use TLS for both producing and consuming. The console producer client `console-producer.sh` does not work with TLS.
1616
17+
> [!Note]
18+
> HDInsight Kafka console producer with version 1.1 does not support SSL.
19+
1720
## Apache Kafka broker setup
1821

1922
The Kafka TLS broker setup will use four HDInsight cluster VMs in the following way:
@@ -68,7 +71,15 @@ Use the following detailed instructions to complete the broker setup:
6871
keytool -keystore kafka.server.keystore.jks -certreq -file cert-file -storepass "MyServerPassword123" -keypass "MyServerPassword123"
6972
scp cert-file sshuser@HeadNode0_Name:~/ssl/wnX-cert-sign-request
7073
```
71-
74+
> [!Note]
75+
> FQDN_WORKER_NODE is Fully Qualified Domain Name of worker node machine.You can get that details from /etc/hosts file in head node
76+
77+
For example,
78+
`wn0-espkaf.securehadooprc.onmicrosoft.com`
79+
`wn0-kafka2.zbxwnwsmpcsuvbjqbmespcm1zg.bx.internal.cloudapp.net`
80+
81+
:::image type="content" source="./media/apache-kafka-ssl-encryption-authentication/etc-hosts.png" alt-text="Screenshot showing etc hosts output" border="true":::
82+
7283
1. On the CA machine run the following command to create ca-cert and ca-key files:
7384

7485
```bash

0 commit comments

Comments
 (0)