[
https://issues.apache.org/jira/browse/DISPATCH-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951289#comment-15951289
]
ASF GitHub Bot commented on DISPATCH-737:
-----------------------------------------
GitHub user ganeshmurthy opened a pull request:
https://github.com/apache/qpid-dispatch/pull/156
DISPATCH-737 - Set the sasl_enabled flag based on some of the paramet…
…ers provided to qdstat and qdmanage
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-737
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-dispatch/pull/156.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #156
----
commit c202711cadb69d4167d08850a558bbf37e18294d
Author: Ganesh Murthy <[email protected]>
Date: 2017-03-31T16:59:35Z
DISPATCH-737 - Set the sasl_enabled flag based on some of the parameters
provided to qdstat and qdmanage
----
> 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.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
