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 #97 from nats-io/no_auth_user

Browse Source 
Documenting no_auth_user
This commit is contained in:
Ginger Collison 2020-05-15 10:08:04 -05:00 committed by GitHub
commit 54548d03a1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
nats-server/configuration/README.md
View File

@ -144,6 +144,7 @@ authorization: {
| :--- | :--- | | :--- | :--- |
| [`authorization`](securing_nats/auth_intro/) | Configuration map for client authentication/authorization. | | [`authorization`](securing_nats/auth_intro/) | Configuration map for client authentication/authorization. |
| [`accounts`](securing_nats/accounts.md) | Configuration map for multi tenancy via accounts. | | [`accounts`](securing_nats/accounts.md) | Configuration map for multi tenancy via accounts. |
| [`no_auth_user`](securing_nats/accounts.md#No-Auth-User) | [Username](securing_nats/auth_intro/username_password.md) present in the [authorization block](securing_nats/auth_intro/README.md) or an [`account`](securing_nats/accounts.md). A client connecting without any form of authentication will be associated with this user, its permissions and account. |
#### Decentralized Authentication and Authorization #### Decentralized Authentication and Authorization

24
nats-server/configuration/securing_nats/accounts.md
View File

@ -166,3 +166,27 @@ It is important to reiterate that:
* service `q.b` is private; only account `B` can send requests to the service. * service `q.b` is private; only account `B` can send requests to the service.
* When `C` publishes a request to `Q`, local `C` clients will see `Q` messages. However, the server will remap `Q` to `pubq.C` and forward the requests to account `A`. * When `C` publishes a request to `Q`, local `C` clients will see `Q` messages. However, the server will remap `Q` to `pubq.C` and forward the requests to account `A`.
## No Auth User
Clients connecting without authentication can be associated with a particular user within an account.
```
accounts: {
A: {
users: [
{user: a, password: a}
]
},
B: {
users: [
{user: b, password: b}
]
}
}
no_auth_user: a
```
The above example shows how clients without authentication can be associated with the user `a` within account `A`.
> Please note that the `no_auth_user` will not work with nkeys.
> The user referenced can also be part of the [authorization](authorization.md) block.