[jira] [Comment Edited] (AMQ-5160) Wildcard subscriptions bypass Authentication / Authorization

["Dejan Bosanac (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-5160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990531#comment-13990531 ] 

Dejan Bosanac edited comment on AMQ-5160 at 5/6/14 10:54 AM:
-------------------------------------------------------------

I was looking a bit more into this. The problem is that we're managing these retained messages in the mqtt filter and sending it directly to the subscription. So it buy-passes all broker interceptors (including security ones). I think the better option would be to reuse subscription recovery policy mechanism

http://activemq.apache.org/subscription-recovery-policy.html

and adapt it for mqtt use-cases. I'll take a stub at refactoring this.


was (Author: dejanb):
I was looking a bit more in this. The problem is that we're managing these retained messages in the mqtt filter and sending it directly to the subscription. So it buy-passes all broker interceptors (including security ones). I think the better option would be to reuse subscription recovery policy mechanism

http://activemq.apache.org/subscription-recovery-policy.html

and adapt it for mqtt use-cases. I'll take a stub at refactoring this.

> Wildcard subscriptions bypass Authentication / Authorization
> ------------------------------------------------------------
>
>                 Key: AMQ-5160
>                 URL: https://issues.apache.org/jira/browse/AMQ-5160
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: MQTT
>    Affects Versions: 5.9.1
>            Reporter: Surf
>            Priority: Critical
>              Labels: authentication, authorization, mqtt, security
>             Fix For: 5.10.0
>
>         Attachments: activemq.xml, groups.properties, login.config, users.properties
>
>
> I am using MQTT on AMQ 5.9.1
> After latest MQTT hardening from [~dhirajsb] , there is an issue of MQTT retained messages.
> Simple case:
> Set Authentication / Authorization for two different TOPICS.
> Send retained message to one topic.
> Try to subscribe "#" with other second user.
> It will show retained messages published by TOPIC 1. 
> here i have attached test configurations.



--
This message was sent by Atlassian JIRA
(v6.2#6252)