[
https://issues.jboss.org/browse/AS7-3150?page=com.atlassian.jira.plugin.s...
]
David White updated AS7-3150:
-----------------------------
Summary: Security for HornetQ (was: Security for HornetQ in AS7)
Affects Version/s: 7.1.0.CR1b
Workaround Description: none - use external security
Description:
Can't find a way to require auth for a JMS connection
http://lists.jboss.org/pipermail/jboss-as7-dev/2011-October/004057.html
suggests there is a bug of omission (perhaps just in the documentation).
Having searched for days, I can't find a solution, hence this bug report.
Component/s: JMS
Steps to Reproduce:
set in standalone-full.xml
<security-settings>
<security-setting match="#">
<permission type="send" roles="admin"/>
<permission type="consume"
roles="admin"/>
<permission type="manage"
roles="admin"/>
</security-setting>
</security-settings>
observe that a new JMS connection requires no authentiation
Security for HornetQ
--------------------
Key: AS7-3150
URL:
https://issues.jboss.org/browse/AS7-3150
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.0.CR1b
Reporter: David White
Can't find a way to require auth for a JMS connection
http://lists.jboss.org/pipermail/jboss-as7-dev/2011-October/004057.html
suggests there is a bug of omission (perhaps just in the documentation).
Having searched for days, I can't find a solution, hence this bug report.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira