[
https://issues.apache.org/activemq/browse/AMQ-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clayton McCarl updated AMQ-1985:
--------------------------------
Description:
from http://activemq.apache.org/security.html - Note that full access rights
should always be given to the ActiveMQ.Advisory destinations, else your client
will receive an exception stating it does not have access rights to these
series of destinations.
<authorizationEntry topic="ActiveMQ.Advisory.>" read="guests,users"
write="guests,users" admin="guests,users"/>
Can this be assumed behind the scenes? This was troubling as a new user adding
security (especially before this was properly documented on Sept 15, 2008).
was:
from <a
href="http://activemq.apache.org/security.html";>http://activemq.apache.org/security.html</a>
- Note that full access rights should always be given to the ActiveMQ.Advisory
destinations, else your client will receive an exception stating it does not
have access rights to these series of destinations.
<authorizationEntry topic="ActiveMQ.Advisory.>" read="guests,users"
write="guests,users" admin="guests,users"/>
Can this be assumed behind the scenes? This was troubling as a new user adding
security (especially before this was properly documented on Sept 15, 2008).
> ActiveMQ Security - grant privileges on ActiveMQ.Advisory.> by default
> ----------------------------------------------------------------------
>
> Key: AMQ-1985
> URL: https://issues.apache.org/activemq/browse/AMQ-1985
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker, Documentation
> Affects Versions: 5.1.0
> Reporter: Clayton McCarl
> Priority: Minor
>
> from http://activemq.apache.org/security.html - Note that full access rights
> should always be given to the ActiveMQ.Advisory destinations, else your
> client will receive an exception stating it does not have access rights to
> these series of destinations.
> <authorizationEntry topic="ActiveMQ.Advisory.>" read="guests,users"
> write="guests,users" admin="guests,users"/>
> Can this be assumed behind the scenes? This was troubling as a new user
> adding security (especially before this was properly documented on Sept 15,
> 2008).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
