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

GitBook: [master] 207 pages modified

Browse Source
This commit is contained in:
Ginger Collison 2021-03-15 18:38:34 +00:00 committed by gitbook-bot
parent 5194cf762e
commit 9f8bb10e6b
No known key found for this signature in database
GPG Key ID: 07D2180C7B12D0FF
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
whats_new_22.md
View File

@ -31,11 +31,11 @@ By specifying a CIDR block restriction for a user, policy can be applied to limi
### Time-Based Account Restrictions
Scoped to the user, you can now specify a specific block of time during the day when applications can connect. For example, permit certain users or applications to access the system during specified business hours, or protect business operations during the busiest parts of the day from batch driven back-office applications that could adversely impact the system when run at the wrong time.
Scoped to the user, you can now [specify a specific block of time](nats-tools/nsc/basics.md#user-authorization) during the day when applications can connect. For example, permit certain users or applications to access the system during specified business hours, or protect business operations during the busiest parts of the day from batch driven back-office applications that could adversely impact the system when run at the wrong time.
### Default User Permissions
Now you can specify [default user permissions](https://github.com/nats-io/nats.docs/tree/4009a69741789af8606c9fd475f92f2bed40ede3/TODO%20Link/README.md) within an account. This significantly reduces efforts around policy, reduces chances for error in permissioning, and simplifies the provisioning of user credentials.
Now you can specify [default user permissions](nats-server/configuration/securing_nats/authorization.md#examples) within an account. This significantly reduces efforts around policy, reduces chances for error in permissioning, and simplifies the provisioning of user credentials.
## WebSockets