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

Merge pull request #68 from nats-io/nkey-link

Browse Source 
Adding a link to client
This commit is contained in:
Ginger Collison 2020-03-16 17:07:46 -05:00 committed by GitHub
commit cb5b640198
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
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 ## 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 ```javascript
const NATS = require('nats'); 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 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. 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 ```sh
nsc add account --name SYS nsc add account --name SYS