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:24:26 UTC

[jira] [Commented] (QPID-6532) make sasl service name configurable

    [ https://issues.apache.org/jira/browse/QPID-6532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950554#comment-14950554 ] 

Ken Giusti commented on QPID-6532:
----------------------------------

QPID-6783 provides a more 'transparent' solution to the different SASL service names used by the supported protocols.

With QPID-6783 it should be possible to avoid using the 'sasl-service-name' configuration option, unless a custom service name is needed.


> make sasl service name configurable
> -----------------------------------
>
>                 Key: QPID-6532
>                 URL: https://issues.apache.org/jira/browse/QPID-6532
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>    Affects Versions: 0.32
>            Reporter: Gordon Sim
>            Assignee: Gordon Sim
>             Fix For: qpid-cpp-0.34
>
>
> At present the service name used with cyrus sasl is build time configurable and defaults to qpidd. It should apparently really be the protocol used, i.e. amqp. To allow for things that assume this (e.g. proton) but also retain backward compatibility, the service name used should be configurable.



--
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