Loading...

XML

Word

Printable

Steps to Reproduce:

Hide

set in messaging section of 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 to send or consume from any destination

Show
set in messaging section of 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 to send or consume from any destination
Forum Reference:
http://community.jboss.org/thread/176900
Workaround Description:

Hide

none - use external security

Show
none - use external security

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.

is related to

AS7-3641 Lock down HornetQ default cluster user