From 18aa250c99bfd9569893e45a1837171d93bee893 Mon Sep 17 00:00:00 2001 From: Matthias Hanel Date: Thu, 20 Feb 2020 19:35:10 -0500 Subject: [PATCH] Remove reference to alice and bob. Signed-off-by: Matthias Hanel --- 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 9ab63dd..28ac17b 100644 --- a/nats-server/configuration/securing_nats/authorization.md +++ b/nats-server/configuration/securing_nats/authorization.md @@ -25,7 +25,7 @@ The `permission` map provides additional properties for configuring a `permissio | `allow` | List of subject names that are allowed to the client | | `deny` | List of subjects that are denied to the client | -**Important Note** It is important to not break request/reply patterns. In some cases \(as shown below\) you need to add rules as above with Alice and Bob for the `_INBOX.>` pattern. If an unauthorized client publishes or attempts to subscribe to a subject that has not been _allow listed_, the action fails and is logged at the server, and an error message is returned to the client. The [allow responses](#allow-responses-map) option can simplify this. +**Important Note** It is important to not break request/reply patterns. In some cases \(as shown [below](#variables)\) you need to add rules for the `_INBOX.>` pattern. If an unauthorized client publishes or attempts to subscribe to a subject that has not been _allow listed_, the action fails and is logged at the server, and an error message is returned to the client. The [allow responses](#allow-responses-map) option can simplify this. ## Allow Responses Map