Skip to content

Commit 2b8e101

Browse files
Add a tip about needing server and client usage in intra-cluster TLS certificates (neo4j#1691)
Copied from the PR neo4j#1688
1 parent b305b92 commit 2b8e101

File tree

2 files changed

+37
-0
lines changed

2 files changed

+37
-0
lines changed

modules/ROOT/pages/clustering/intra-cluster-encryption.adoc

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,24 @@ Under SSL, an endpoint can authenticate itself using certificates managed by a x
2424
It should be noted that the deployment of a secure key management infrastructure is beyond the scope of this manual, and should be entrusted to experienced security professionals.
2525
The example deployment illustrated below is for reference purposes only.
2626

27+
[TIP]
28+
====
29+
If setting up intra-cluster encryption as part of a cluster configuration, ensure that the certificates used on the cluster endpoint support server and client usage.
30+
This is because when connecting between the Neo4j servers for clustering, each server uses its own certificate to authenticate as a client on the connection to another server.
31+
32+
This could be verified from within the certificate details:
33+
34+
----
35+
openssl x509 -in public.crt -noout -text
36+
----
37+
38+
We should see that the X509v3 Extended Key Usage section shows both the usages listed:
39+
40+
----
41+
X509v3 Extended Key Usage:
42+
TLS Web Server Authentication, TLS Web Client Authentication
43+
----
44+
====
2745

2846
[[causal-clustering-intra-cluster-encryption-example-deployment]]
2947
== Example deployment

modules/ROOT/pages/security/ssl-framework.adoc

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -85,6 +85,25 @@ Valid trusted certificates can be generated for free using non-profit CAs such a
8585

8686
The instructions on this page assume that you have already obtained the required certificates from the CA.
8787

88+
[TIP]
89+
====
90+
If setting up intra-cluster encryption as part of a cluster configuration, ensure that the certificates used on the cluster endpoint support server and client usage.
91+
This is because when connecting between the Neo4j servers for clustering, each server uses its own certificate to authenticate as a client on the connection to another server.
92+
93+
This could be verified from within the certificate details:
94+
95+
----
96+
openssl x509 -in public.crt -noout -text
97+
----
98+
99+
We should see that the X509v3 Extended Key Usage section shows both the usages listed:
100+
101+
----
102+
X509v3 Extended Key Usage:
103+
TLS Web Server Authentication, TLS Web Client Authentication
104+
----
105+
====
106+
88107
=== Validate the key and the certificate
89108

90109
If you need, you can validate the key file and the certificate as follows:

0 commit comments

Comments
 (0)