Hi Ganesh,

thanks !
Paolo.

Paolo PatiernoSenior Software Engineer (IoT) @ Red Hat
Microsoft MVP on Windows Embedded & IoTMicrosoft Azure Advisor 
Twitter : @ppatierno
Linkedin : paolopatierno
Blog : DevExperience

> Date: Wed, 1 Jun 2016 12:05:38 -0400
> From: gmur...@redhat.com
> To: users@qpid.apache.org
> Subject: Re: Qdstat, SASL and user with @domain
> 
> Hi Paolo,
>    There is a dispatch issue 
> https://issues.apache.org/jira/browse/DISPATCH-233 which will deal with 
> exactly what you are talking about. The fix to DISPATCH-233 will be available 
> in 0.7 release.
> Thanks.
> 
> ----- Original Message -----
> > From: "Paolo Patierno" <ppatie...@live.com>
> > To: users@qpid.apache.org
> > Sent: Wednesday, June 1, 2016 11:56:08 AM
> > Subject: Qdstat, SASL and user with @domain
> > 
> > Hi all,
> > 
> > I have configured a router with SASL PLAIN authentication and the SASL db 
> > was
> > created using the Cyrus tool (saslpasswd2).
> > Using this tool you can specify or not a domain but if you don't specify it,
> > the tool adds a default one (the machine hostname on which it's running).
> > In any case you have user like : <name>@<domain>.
> > 
> > Using Python client as example I'm able to connect to the router using the
> > complete user as <name>@<domain> (it doesn't work with just <name>)
> > 
> > Now ... the problem is with qdstat which needs SASL to connect to the router
> > to get information. Using the -b option in the form :
> > 
> > -b <name>@<domain>:<password>@localhost:5672
> > 
> > the parser fails ... too much "@" :-)
> > 
> > It could be useful to have SASL user and password parameters for the qdstat
> > tool in this scenario.
> > 
> > Thanks,
> > Paolo.
> > 
> > 
> > Paolo PatiernoSenior Software Engineer (IoT) @ Red Hat
> > Microsoft MVP on Windows Embedded & IoTMicrosoft Azure Advisor
> > Twitter : @ppatierno
> > Linkedin : paolopatierno
> > Blog : DevExperience
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 
                                          

Reply via email to