zergduan commented on issue #4527: URL: https://github.com/apache/rocketmq/issues/4527#issuecomment-1169108366
Based on the content of the document: https://github.com/apache/rocketmq/blob/e05b098327d0781362121c65e1c9445c0cb0684b/docs/cn/Configuration_TLS.md I have some questions as below: a. For rocketmq 4.9.2 and later versions, must TLS set up in mutual authentication? Can it be set in server-side authentication? b. As the step 3.2 in above document: >> Edit runbroker SH, in Java_ The following contents are added to opt: >> JAVA_ OPT="${JAVA_OPT} -Dorg.apache.rocketmq.remoting.ssl.mode=enforcing -Dtls.config.file=/opt/rocketmq-4.9.3/conf/tls.properties -Dtls.enable=true" I didn't find the corresponding content of the source code for the paramemter "org.apache.rocketmq.remoting.ssl.mode". Is it wrong? c. It seems the value of parameter "tls.server.need.client.auth" controls whether client authentication (mutual authentication) is enabled, is it right? but what are the parameter "tls.server.authClient" and "tls.client.authServer" used for? d. It seems to be some contradiction In the above document: the parameter "tls.client.authServer" is set to false (in tls.properties file) on borker and namesrv, but set to true (in java_opt environment variable) on producer and consumer. Why? e. When we finish all steps in the above document. Will the interaction between the broker and the namesrv also be subject to client authentication? For example, the broker reports its own status to namesrv (heartbeat), which is also a TLS encrypted communication? The mean When a broker reports to a namesrv, the broker as a client, also needs to be verified by the namesrv (client authentication), it is Right? f. If we enable TLS according to the steps in the document, does it affect the rocketmq-dashboard connection to rocketmq cluster (namesrv) ? -- 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]
