[
https://issues.apache.org/jira/browse/DISPATCH-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089891#comment-16089891
]
Ganesh Murthy commented on DISPATCH-737:
----------------------------------------
Hi Jakub,
I was looking at
https://github.com/apache/qpid-dispatch/blob/master/python/qpid_dispatch_internal/tools/command.py#L134
and it does look like when you specify either a mech or a user/password, SASL
is enabled as seen in
https://github.com/apache/qpid-dispatch/blob/master/python/qpid_dispatch/management/client.py#L89
Are you seeing otherwise?
Thanks.
> 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]
