[
https://issues.apache.org/activemq/browse/AMQ-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39499
]
Tom Samplonius commented on AMQ-1272:
-------------------------------------
Here is the config that I'm using:
<plugins>
<simpleAuthenticationPlugin>
<users>
<authenticationUser username="system" password="manager"
groups="producers,consumers,admins" />
<authenticationUser username="frontend" password="manager"
groups="producers" />
<authenticationUser username="backend" password="manager"
groups="consumers" />
</users>
</simpleAuthenticationPlugin>
<authorizationPlugin>
<map>
<authorizationMap>
<authorizationEntries>
<authorizationEntry queue=">" read="backend" write="frontend"
admin="admins" />
</authorizationEntries>
</authorizationMap>
</map>
</authorizationPlugin>
</plugins>
> Stomp protocol does not correctly check authentication (security hole)
> ----------------------------------------------------------------------
>
> Key: AMQ-1272
> URL: https://issues.apache.org/activemq/browse/AMQ-1272
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.0.0
> Environment: 4.2-SNAPSHOT
> Reporter: Tom Samplonius
> Priority: Blocker
> Fix For: 4.1.2, 5.0.0
>
> Attachments: stomp.diff
>
>
> ActiveMQ does not correctly validate the username and password of Stomp
> clients. A security exception is generated, but ignored, leaving the client
> connected, and with full and unrestricted access to ActiveMQ.
> Further description, and a partial patch:
> http://www.nabble.com/Getting-Stomp-support-to-a-usable-state...-tf3858629s2354.html#a11060452
>
> BTW, while the patch in the above post, is crude, however, leaving
> unauthenticated users connected with full-access makes ActiveMQ and Stomp
> pretty unusable. So please apply the path, rather than do nothing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
