crossoverJie commented on code in PR #22694:
URL: https://github.com/apache/pulsar/pull/22694#discussion_r1630520831


##########
pip/pip-351.md:
##########
@@ -0,0 +1,166 @@
+<!--
+RULES
+* Never place a link to an external site like Google Doc. The proposal should 
be in this issue entirely.
+* Use a spelling and grammar checker tools if available for you (there are 
plenty of free ones).
+
+PROPOSAL HEALTH CHECK
+I can read the design document and understand the problem statement and what 
you plan to change *without* resorting to a couple of hours of code reading 
just to start having a high level understanding of the change.
+
+IMAGES
+If you need diagrams, avoid attaching large files. You can use 
[MermaidJS]([url](https://mermaid.js.org/)) as a simple language to describe 
many types of diagrams.
+
+THIS COMMENTS
+Please remove them when done.
+-->
+
+# PIP-351: Additional options for Pulsar-Test client to support KeyStore based 
TLS
+
+# Background knowledge
+
+<!--
+Describes all the knowledge you need to know in order to understand all the 
other sections in this PIP
+
+* Give a high level explanation on all concepts you will be using throughout 
this document. For example, if you want to talk about Persistent Subscriptions, 
explain briefly (1 paragraph) what this is. If you're going to talk about 
Transaction Buffer, explain briefly what this is. 
+  If you're going to change something specific, then go into more detail about 
it and how it works. 
+* Provide links where possible if a person wants to dig deeper into the 
background information. 
+
+DON'T
+* Do not include links *instead* explanation. Do provide links for further 
explanation.
+
+EXAMPLES
+* See [PIP-248](https://github.com/apache/pulsar/issues/19601), Background 
section to get an understanding on how you add the background knowledge needed.
+  (They also included the motivation there, but ignore it as we place that in 
Motivation section explicitly).
+-->
+
+In both Pulsar Client and Pulsar Admin, we support the use of KeyStores. This 
feature is provided by means of the boolean
+"useKeyStoreTls". The boolean is also the only way authentication mechanisms 
such as AuthenticationKeyStoreTls can be utilised
+properly, as the logic to use keystores for SSL Connections, from either 
ClientConfigurationData stored in Pulsar Admin/Client
+or AuthData hinges on the "useKeyStoreTls" boolean as can be seen below:
+
+<b>AsyncHttpConnector.java</b>
+```java
+if (conf.isUseKeyStoreTls()) {
+                    KeyStoreParams params = authData.hasDataForTls() ? 
authData.getTlsKeyStoreParams() :

Review Comment:
   It is recommended to adjust the indentation of the code.



-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to