gogrlx/nats-server
1
0
Fork 0
mirror of https://github.com/gogrlx/nats-server.git synced 2026-04-02 03:38:42 -07:00
Code Issues Packages Projects Releases Wiki Activity

Update to gnatsd/README.md fixing authorization section addressing issue #662 "_INBOX.>" permission

Browse Source
This commit is contained in:
ainsley
2018-05-21 11:21:46 -05:00
parent 99b6bb30d0
commit e453d78f4a
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -555,7 +555,7 @@ authorization {
} }
REQUESTOR = { REQUESTOR = {
publish = ["req.foo", "req.bar"] publish = ["req.foo", "req.bar"]
subscribe = "_INBOX.*" subscribe = "_INBOX.>"
} }
DEFAULT_PERMISSIONS = { DEFAULT_PERMISSIONS = {
publish = "SANDBOX.*" publish = "SANDBOX.*"
@@ -577,7 +577,7 @@ Bob is REQUESTOR and can publish requests on subjects "req.foo" or "req.bar", an
Joe has no permission grant and therefore inherits the default permission set. You set the inherited default permissions by assigning them to the `default_permissions` entry inside of the `authorization` configuration block. Joe has no permission grant and therefore inherits the default permission set. You set the inherited default permissions by assigning them to the `default_permissions` entry inside of the `authorization` configuration block.
Note that `_INBOX.*` subscribe permissions must be granted in order to use the request APIs in Apcera supported clients. If an unauthorized client publishes or attempts to subscribe to a subject, the action fails and is logged at the server, and an error message is returned to the client. Note that `_INBOX.>` subscribe permissions must be granted in order to use the request APIs in Synadia supported clients. If an unauthorized client publishes or attempts to subscribe to a subject, the action fails and is logged at the server, and an error message is returned to the client.
### TLS ### TLS