[
https://issues.apache.org/jira/browse/DISPATCH-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089138#comment-16089138
]
Jakub Scholz commented on DISPATCH-737:
---------------------------------------
Hi Ganesh,
Before the last changes in this issue, this command seemed to work:
{code}
qdstat -g -b admin:[email protected]:5672
{code}
Now I have to use this:
{code}
qdstat -g -b admin:[email protected]:5672 --sasl-mechanism=DIGEST-MD5
{code}
Is it really intentional that even when I specify username and password, SASL
isn't enabled automatically and I have to specify the mechanism?
Thanks & Regards
Jakub
> qdstat and qdmanage always force sasl exchange
> ----------------------------------------------
>
> Key: DISPATCH-737
> URL: https://issues.apache.org/jira/browse/DISPATCH-737
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Management Agent
> Affects Versions: 0.7.0
> Reporter: Ganesh Murthy
> Assignee: Ganesh Murthy
> Fix For: 1.0.0
>
>
> qdmanage and qdstat use the Proton Python blocking API to do its work. The
> Python API offers a flag called sasl_enabled and it is always set to true
> which always initiates a SASL exchange. SASL should only be invoked when
> mechanisms are explicitly provided by qdstat and qdmanage via its
> sasl-mechanisms or sasl-username or sasl-password or ssl parameters
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
