[jira] [Updated] (AMQ-5233) MQTT broker with ACL, try to connect using bad credential sends first connection event and after disconnect event to client

["Sandro Salari (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sandro Salari updated AMQ-5233:
-------------------------------

      Description: 
Configure broker with :

    <amq:broker useJmx="false" persistent="false">
        <amq:transportConnectors>
            <amq:transportConnector name="mqtt" uri="${jms.brokerurl}">            
        </amq:transportConnectors>
        <amq:networkConnectors/>

        <amq:plugins>
            <amq:simpleAuthenticationPlugin>
                <amq:users>
                    <amq:authenticationUser username="test" password="test" groups="admins,guests,users" />
                </amq:users>
            </amq:simpleAuthenticationPlugin>
            <amq:authorizationPlugin>
                <amq:map>
                    <amq:authorizationMap>
                        <amq:authorizationEntries>
                            <amq:authorizationEntry queue=">" read="admins" write="admins" admin="admins" />
                            <amq:authorizationEntry topic=">" read="admins" write="admins" admin="admins" />
                            <amq:authorizationEntry topic="ActiveMQ.Advisory.>" read="admins" write="admins" admin="admins"/>
                        </amq:authorizationEntries>
                    </amq:authorizationMap>
                </amq:map>
            </amq:authorizationPlugin>
        </amq:plugins>
    </amq:broker>

Connecting with mosquittolib (C) with bad credential rise first "on_connection" event as the connection is OK, and next "on_disconnection" event. Expected behavior is failed connection with BAD CREDENTIAL reported error form broker.


  was:
Configure broker to expose its URi via zeroconf agent using :

{code:xml|title=queueContext.xml|borderStyle=solid}
<amq:transportConnectors>
    <amq:transportConnector name="mqtt" uri="${jms.brokerurl}" discoveryUri="zeroconf://mainnode"/>			
</amq:transportConnectors>
{code}

The service exposed is not discovered by ios or iosX Bonjour browser   (you can use [Bonjour Browser|https://itunes.apple.com/it/app/discovery-bonjour-browser/id305441017?mt=8] on mac  to test it) 



       Patch Info:   (was: Patch Available)
      Environment: 
Windows 7 - 64 bit
Eclipse Kepler
JDK 1.7
Spring 4.0
MosquittoLib (C) on iOS


  was:
Windows 7 - 64 bit
Eclipse Kepler
JDK 1.7
Spring 4.0


    Fix Version/s:     (was: 5.10.0)
           Labels: acl broker connection disconnection mqtt  (was: )
       Issue Type: Bug  (was: Improvement)
          Summary: MQTT broker with ACL, try to connect using bad credential sends first connection event and after disconnect event to client   (was: MQTT Boreker with ACL, try to connect using bad credential sends first connection event and after disconnect event to client )

> MQTT broker with ACL, try to connect using bad credential sends first connection event and after disconnect event to client 
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-5233
>                 URL: https://issues.apache.org/jira/browse/AMQ-5233
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.9.1
>         Environment: Windows 7 - 64 bit
> Eclipse Kepler
> JDK 1.7
> Spring 4.0
> MosquittoLib (C) on iOS
>            Reporter: Sandro Salari
>            Priority: Minor
>              Labels: acl, broker, connection, disconnection, mqtt
>
> Configure broker with :
>     <amq:broker useJmx="false" persistent="false">
>         <amq:transportConnectors>
>             <amq:transportConnector name="mqtt" uri="${jms.brokerurl}">            
>         </amq:transportConnectors>
>         <amq:networkConnectors/>
>         <amq:plugins>
>             <amq:simpleAuthenticationPlugin>
>                 <amq:users>
>                     <amq:authenticationUser username="test" password="test" groups="admins,guests,users" />
>                 </amq:users>
>             </amq:simpleAuthenticationPlugin>
>             <amq:authorizationPlugin>
>                 <amq:map>
>                     <amq:authorizationMap>
>                         <amq:authorizationEntries>
>                             <amq:authorizationEntry queue=">" read="admins" write="admins" admin="admins" />
>                             <amq:authorizationEntry topic=">" read="admins" write="admins" admin="admins" />
>                             <amq:authorizationEntry topic="ActiveMQ.Advisory.>" read="admins" write="admins" admin="admins"/>
>                         </amq:authorizationEntries>
>                     </amq:authorizationMap>
>                 </amq:map>
>             </amq:authorizationPlugin>
>         </amq:plugins>
>     </amq:broker>
> Connecting with mosquittolib (C) with bad credential rise first "on_connection" event as the connection is OK, and next "on_disconnection" event. Expected behavior is failed connection with BAD CREDENTIAL reported error form broker.



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