<font size=2 face="sans-serif">I guess I am not able to clarify my question.
</font>
<br>
<br><font size=2 face="sans-serif">Ok let me pose this like , is there
any other mode of authentication other than TLS ?</font>
<br>
<br><font size=2 face="sans-serif">When we create topics , is there any
feature of role / user based access of those topics?</font>
<br><font size=2 face="sans-serif"><br>
Thanks and Regards,<br>
Ankur Chakraborty<br>
</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Michael Klishin <mklishin@gopivotal.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Ankur5 C <ankur5.c@tcs.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">Legacy list about RabbitMQ
<rabbitmq-discuss@lists.rabbitmq.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">22-07-2014 17:22</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [rabbitmq-discuss]
MQTT login failed for "guest" access_refused even after mentioning
loopback_users</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>On 22 July 2014 at 15:41:40, Ankur5 C (ankur5.c@tcs.com)
wrote:<br>
> > So if I do not use SSL , in that case how does the authentication
<br>
> occur?<br>
<br>
If you configure RabbitMQ to verify peer, the client will be authenticated.<br>
Paho can be configured to perform TLS verification, too.<br>
<br>
</font></tt><a href=http://www.rabbitmq.com/ssl.html><tt><font size=2>http://www.rabbitmq.com/ssl.html</font></tt></a><tt><font size=2><br>
<br>
Different clients expose different APIs for enabling/disabling peer verification.<br>
There are 3 examples that demonstrate how MQTT clients can be set up to
use TLS<br>
with peer verification, including 2 Paho clients (Java and Python):<br>
<br>
</font></tt><a href="https://github.com/michaelklishin/mqtt-tls-playground"><tt><font size=2>https://github.com/michaelklishin/mqtt-tls-playground</font></tt></a><tt><font size=2><br>
<br>
> Anyone who is aware of the uri can post data to a topic with <br>
> a client id ?<br>
<br>
You do not post data to URIs in MQTT. You open a long-running connection<br>
using a URI and client-id, then publish messages using a separate protocol<br>
frame (which clients expose as a separate API function/method).<br>
<br>
In Paho, the method is MqttClient#publish:<br>
</font></tt><a href=http://www.eclipse.org/paho/files/javadoc/org/eclipse/paho/client/mqttv3/MqttClient.html#publish(java.lang.String><tt><font size=2>http://www.eclipse.org/paho/files/javadoc/org/eclipse/paho/client/mqttv3/MqttClient.html#publish(java.lang.String</font></tt></a><tt><font size=2>,
byte[], int, boolean)<br>
<br>
Sorry to point this out but this is really basic ,<br>
a software engineer should be able to figure this out on her own quite
quickly.<br>
<br>
> What is the significance of the user and pass (mentioned as default
<br>
> user and pass) mentioned in the rabbit config file?<br>
<br>
We are going in circles on this. This is documented quite clearly:<br>
</font></tt><a href=http://www.rabbitmq.com/mqtt.html><tt><font size=2>http://www.rabbitmq.com/mqtt.html</font></tt></a><tt><font size=2><br>
<br>
> I am using the default one and using the tag loopback_users, [] <br>
> for connecting from remote host. All is working fine.<br>
<br>
That can work but now it is possible to connect to your RabbitMQ node<br>
using well-known credentials of an administrative user. Doesn't sound incredibly<br>
secure to me.<br>
-- <br>
MK <br>
<br>
Staff Software Engineer, Pivotal/RabbitMQ<br>
</font></tt>
<br><p>=====-----=====-----=====<br>
Notice: The information contained in this e-mail<br>
message and/or attachments to it may contain <br>
confidential or privileged information. If you are <br>
not the intended recipient, any dissemination, use, <br>
review, distribution, printing or copying of the <br>
information contained in this e-mail message <br>
and/or attachments to it are strictly prohibited. If <br>
you have received this communication in error, <br>
please notify us by reply e-mail or telephone and <br>
immediately and permanently delete the message <br>
and any attachments. Thank you</p>
<p></p>