From da84b99c91de29f3af09e61b2715f56c3a311a14 Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Thu, 20 Feb 2020 18:25:15 -0600 Subject: [PATCH] Update authorization.md --- nats-server/configuration/securing_nats/authorization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nats-server/configuration/securing_nats/authorization.md b/nats-server/configuration/securing_nats/authorization.md index 3fbef06..9ab63dd 100644 --- a/nats-server/configuration/securing_nats/authorization.md +++ b/nats-server/configuration/securing_nats/authorization.md @@ -4,7 +4,7 @@ The NATS server supports authorization using subject-level permissions on a per- Each permission specifies the subjects the user can publish to and subscribe to. The parser is generous at understanding what the intent is, so both arrays and singletons are processed. For more complex configuration, you can specify a `permission` object which explicitly allows or denies subjects. The specified subjects can specify wildcards as well. Permissions can make use of [variables](../README.md#variables). -A special field inside the authorization map is `default_permissions`. When present, it contains permissions that apply to user that do not have permissions associated with them. +A special field inside the authorization map is `default_permissions`. When present, it contains permissions that apply to users that do not have permissions associated with them. ## Permissions Configuration Map