Skip to content

Commit 4a759d9

Browse files
Add a small clarification on using sub-CA for a cluster (neo4j#1790) (neo4j#1794)
1 parent 83c8b5a commit 4a759d9

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

modules/ROOT/pages/clustering/setup/encryption.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -66,8 +66,8 @@ This means that the server now has the capability of establishing trust with oth
6666
[CAUTION]
6767
====
6868
Be sure to exercise caution when using CA certificates in the `trusted` directory, as any certificates signed by that CA are then trusted to join the cluster.
69-
For this reason, never use a public CA to sign certificates for your cluster.
70-
Instead, use an intermediate certificate or a CA certificate which originates from and is controlled by your organization.
69+
Never use a public CA or your internal root CA to sign certificates for your cluster.
70+
Instead, use an intermediate certificate or a CA certificate which originates from and is controlled by your organization, and is only used for that specific cluster.
7171
====
7272

7373
In this example a mutual authentication setup is deployed, which means that both ends of a channel have to authenticate.

0 commit comments

Comments
 (0)