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

Adding a link to client

Browse Source 
Signed-off-by: Matthias Hanel <mh@synadia.com>
This commit is contained in:
Matthias Hanel 2020-03-11 19:49:02 -04:00
parent c36e4d018e
commit 70f1bd7263
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
nats-server/configuration/securing_nats/auth_intro/nkey_auth.md
View File

@ -36,7 +36,7 @@ Note that the user section sets the `nkey` property \(user/password/token proper
## Client Configuration
Now that you have a user nkey, let's configure a client to use it for authentication. As an example, here are the connect options for the node client:
Now that you have a user nkey, let's configure a [client](../../../../developing-with-nats/security/nkey.md) to use it for authentication. As an example, here are the connect options for the node client:
```javascript
const NATS = require('nats');
@ -69,7 +69,7 @@ that could be used in the future, and then base from that configuration to creat
NKEYS static config using the same shared public nkeys for the accounts and then use
clustering routes to bridge the two different auth setups during the transition.
For example, creating the following initial setup using [NSC](/nsc/readme.md):
For example, creating the following initial setup using [NSC](../../../../nats-tools/nsc/README.md):
```sh
nsc add account --name SYS