You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ken Giusti (JIRA)" <ji...@apache.org> on 2015/10/09 17:02:27 UTC

[jira] [Reopened] (QPID-6767) qpidd tools don't allow sasl service name to be changed

     [ https://issues.apache.org/jira/browse/QPID-6767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ken Giusti reopened QPID-6767:
------------------------------

Andrew has supplied a cleaner fix which causes the broker to dynamically set the proper sasl service name based on connection's protocol: 'amqp' for AMQP 1.0 connections, 'qpidd' for 0_10. 

This behavior is by default, and can be overridden by the broker's 'sasl-service-name' configuration setting (it will be used for all connections regardless of protocol)

> qpidd tools don't allow sasl service name to be changed
> -------------------------------------------------------
>
>                 Key: QPID-6767
>                 URL: https://issues.apache.org/jira/browse/QPID-6767
>             Project: Qpid
>          Issue Type: Bug
>          Components: Python Tools
>    Affects Versions: 0.32
>            Reporter: Gordon Sim
>            Assignee: Ken Giusti
>             Fix For: qpid-tools-next, qpid-python-next
>
>         Attachments: sasl-service-name-full.patch
>
>
> QPID-6532 made the sasl service name that qpidd uses configurable. However if this is changed then the python based cli tools are unable to use mechanisms that rely on it (e.g. DIGEST-MD5, GSSAPI) as they have no way to configure the service name used from the 'qpidd' default.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org