From e5f7e7005894b845d8270b9c4b0715674cc223a9 Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Mon, 13 Apr 2020 16:31:38 -0500 Subject: [PATCH] Update tls.md --- developing-with-nats/security/tls.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developing-with-nats/security/tls.md b/developing-with-nats/security/tls.md index 041ab24..d9b1533 100644 --- a/developing-with-nats/security/tls.md +++ b/developing-with-nats/security/tls.md @@ -6,7 +6,7 @@ While authentication limits which clients can connect, TLS can be used to encryp Using TLS to connect to a server that verifies the client's identity is straightforward. The client has to provide a certificate and private key. The NATS client will use these to prove it's identity to the server. For the client to verify the server's identity, the CA certificate is provided as well. -Use example certificates created in [self signed certificates for testing](../../nats-server/configuration/securing_nats/tls.md#creating-self-signed-certificates-for-festing). +Use example certificates created in [self signed certificates for testing](../../nats-server/configuration/securing_nats/tls.md#creating-self-signed-certificates-for-testing). ```bash > nats-server --tls --tlscert=server-cert.pem --tlskey=server-key.pem --tlscacert rootCA.pem --tlsverify