You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/07/10 19:01:00 UTC
[jira] [Commented] (DISPATCH-737) qdstat and qdmanage always force
sasl exchange
[ https://issues.apache.org/jira/browse/DISPATCH-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080883#comment-16080883 ]
ASF GitHub Bot commented on DISPATCH-737:
-----------------------------------------
Github user ganeshmurthy closed the pull request at:
https://github.com/apache/qpid-dispatch/pull/156
> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org