|
|
|
@ -536,13 +536,17 @@
|
|
|
|
|
# comment.
|
|
|
|
|
# Topic access is added with lines of the format:
|
|
|
|
|
#
|
|
|
|
|
# topic [read|write|readwrite] <topic>
|
|
|
|
|
# topic [read|write|readwrite|deny] <topic>
|
|
|
|
|
#
|
|
|
|
|
# The access type is controlled using "read", "write" or "readwrite". This
|
|
|
|
|
# parameter is optional (unless <topic> contains a space character) - if not
|
|
|
|
|
# given then the access is read/write. <topic> can contain the + or #
|
|
|
|
|
# The access type is controlled using "read", "write", "readwrite" or "deny".
|
|
|
|
|
# This parameter is optional (unless <topic> contains a space character) - if
|
|
|
|
|
# not given then the access is read/write. <topic> can contain the + or #
|
|
|
|
|
# wildcards as in subscriptions.
|
|
|
|
|
#
|
|
|
|
|
# The "deny" option can used to explicity deny access to a topic that would
|
|
|
|
|
# otherwise be granted by a broader read/write/readwrite statement. Any "deny"
|
|
|
|
|
# topics are handled before topics that grant read/write access.
|
|
|
|
|
#
|
|
|
|
|
# The first set of topics are applied to anonymous clients, assuming
|
|
|
|
|
# allow_anonymous is true. User specific topic ACLs are added after a
|
|
|
|
|
# user line as follows:
|
|
|
|
|