From 819405bd74dea31d0c7b4f70d5660e240cefd644 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Wawrzyniec=20Niewodnicza=C5=84ski?= Date: Thu, 10 Jan 2019 15:49:06 +0000 Subject: [PATCH] Fix one important block --- docs/source/corda-configuration-file.rst | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/docs/source/corda-configuration-file.rst b/docs/source/corda-configuration-file.rst index 598598fbb5..cc5093f2a1 100644 --- a/docs/source/corda-configuration-file.rst +++ b/docs/source/corda-configuration-file.rst @@ -382,11 +382,7 @@ rpcAddress rpcSettings Options for the RPC server exposed by the Node. - **Important: The RPC SSL certificate is used by RPC clients to authenticate the connection. - The Node operator must provide RPC clients with a truststore containing the certificate they can trust. - We advise Node operators to not use the P2P keystore for RPC. - The node can be run with the "generate-rpc-ssl-settings" command, which generates a secure keystore and truststore that can be used to secure the RPC connection. - You can use this if you have no special requirements.** + **Important: The RPC SSL certificate is used by RPC clients to authenticate the connection. The Node operator must provide RPC clients with a truststore containing the certificate they can trust. We advise Node operators to not use the P2P keystore for RPC. The node can be run with the "generate-rpc-ssl-settings" command, which generates a secure keystore and truststore that can be used to secure the RPC connection. You can use this if you have no special requirements.** address host and port for the RPC server binding.