TLS Authentication in clusters
When setting up clusters, all servers in the cluster, if using TLS, will both verify the connecting endpoints and the server responses. So certificates are checked in both directions. Certificates can be configured only for the server's cluster identity, keeping client and server certificates separate from cluster formation.
TLS Mutual Authentication is the only way of securing routes.
1
cluster {
2
listen: 127.0.0.1:4244
3
4
tls {
5
# Route cert
6
cert_file: "./configs/certs/srva-cert.pem"
7
# Private key
8
key_file: "./configs/certs/srva-key.pem"
9
# Optional certificate authority verifying connected routes
10
# Required when we have self-signed CA, etc.
11
ca_file: "./configs/certs/ca.pem"
12
}
13
# Routes are actively solicited and connected to from this server.
14
# Other servers can connect to us if they supply the correct credentials
15
# in their routes definitions from above.
16
routes = [
17
nats-route://127.0.0.1:4246
18
]
19
}
Copied!
Export as PDF
Copy link
Edit on GitHub