You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/clustering/setup/encryption.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,8 +66,8 @@ This means that the server now has the capability of establishing trust with oth
66
66
[CAUTION]
67
67
====
68
68
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.
71
71
====
72
72
73
73
In this example a mutual authentication setup is deployed, which means that both ends of a channel have to authenticate.
0 commit comments