qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DISPATCH-116) Qpid dispatch management tools do not use SSL and SASL correctly.
Date Tue, 17 Feb 2015 21:59:11 GMT

    [ https://issues.apache.org/jira/browse/DISPATCH-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14324967#comment-14324967

ASF subversion and git services commented on DISPATCH-116:

Commit 1660512 from [~aconway] in branch 'dispatch/trunk'
[ https://svn.apache.org/r1660512 ]

DISPATCH-116: Managment clients and tests use anonymous@ to trigger SASL connection by proton.

Recent changes in proton mean that by default it does no SASL handshake on connection.
Dispatch requires SASL, using "anonymous@" in the connection URL for proton triggers
the SASL handshake.

> Qpid dispatch management tools do not use SSL and SASL correctly.
> -----------------------------------------------------------------
>                 Key: DISPATCH-116
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-116
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Management Agent
>    Affects Versions: 0.4
>            Reporter: Alan Conway
>            Assignee: Alan Conway
>             Fix For: 0.4
> Recent changes in proton mean that proton clients do not do a SASL handshake by default
unless there is a username in the connection URL.
> Since dispatch requires SASL the dispatch management tools need to add anonymous@ to
connection URLs if there is not aleady a username specified, this enables SASL.
> The tools also do not appear to be applying SSL connectoin options correctly.

This message was sent by Atlassian JIRA

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

View raw message