Skip to content

Commit

Permalink
DOC: added a clarification about a token usage
Browse files Browse the repository at this point in the history
  • Loading branch information
sarbash committed Aug 20, 2017
1 parent 050049c commit 855272b
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -468,6 +468,9 @@ authorization {
}
```

>If you chose to use a token for client's authentication and generate the token by `/util/mkpassword.go` then you should use the generated bcrypt hash as the token in server's config as written above and the generated pass as the token in client's config.
Note that the token for the client is the generated pass and the token for the server is the generated bcrypt hash.

**Multi-user authentication**

You can enable multi-user authentication using a NATS server configuration file that defines user credentials (`user` and `password`), and optionally `permissions`, for two or more users. Multi-user authentication leverages [variables](#variables).
Expand Down

0 comments on commit 855272b

Please sign in to comment.