Add a note for configuring `tlsTrustStorePath` along with `useKeyStoreTls`.
@@ -158,10 +158,10 @@ Optional settings that may worth consider:
By default, it is not set.
### Configuring Clients
-This is similar to [TLS encryption configuing for client with PEM type](security-tls-transport.md#Client configuration).
-For a a minimal configuration, user need to provide the TrustStore information.
+This is similar to [TLS encryption configuing for client with PEM type](security-tls-transport.md#client-configuration).
+For a minimal configuration, you need to provide the TrustStore information.
-e.g.
+For example:
1. for [Command-line tools](reference-cli-tools.md) like [`pulsar-admin`](reference-cli-tools#pulsar-admin), [`pulsar-perf`](reference-cli-tools#pulsar-perf), and [`pulsar-client`](reference-cli-tools#pulsar-client) use the `conf/client.conf` config file in a Pulsar installation.
```properties
@@ -197,6 +197,8 @@ e.g.
.build();
```
+> **Note:** Please configure `tlsTrustStorePath` when you set `useKeyStoreTls` to `true`.
+
## TLS authentication with KeyStore configure
This similar to [TLS authentication with PEM type](security-tls-authentication.md)
@@ -244,7 +246,7 @@ webSocketServiceEnabled=false
Besides the TLS encryption configuring. The main work is configuring the KeyStore, which contains a valid CN as client role, for client.
-e.g.
+For example:
1. for [Command-line tools](reference-cli-tools.md) like [`pulsar-admin`](reference-cli-tools#pulsar-admin), [`pulsar-perf`](reference-cli-tools#pulsar-perf), and [`pulsar-client`](reference-cli-tools#pulsar-client) use the `conf/client.conf` config file in a Pulsar installation.
```properties
@@ -288,6 +290,8 @@ e.g.
.build();
```
+> **Note:** Please configure `tlsTrustStorePath` when you set `useKeyStoreTls` to `true`.
+
## Enabling TLS Logging
You can enable TLS debug logging at the JVM level by starting the brokers and/or clients with `javax.net.debug` system property. For example:
