taigrr/nats.docs
1
0
Fork 0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00
Code Issues Projects Releases Wiki Activity

Update tls.md

Browse Source
This commit is contained in:
Ginger Collison 2020-04-13 16:31:38 -05:00 committed by GitHub
parent 9443b0ced5
commit e5f7e70058
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
developing-with-nats/security/tls.md
View File

@ -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. 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 ```bash
> nats-server --tls --tlscert=server-cert.pem --tlskey=server-key.pem --tlscacert rootCA.pem --tlsverify > nats-server --tls --tlscert=server-cert.pem --tlskey=server-key.pem --tlscacert rootCA.pem --tlsverify