qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Stitcher (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (PROTON-1884) [c] example broker does not configure SASL correctly
Date Tue, 17 Jul 2018 22:00:00 GMT

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

Andrew Stitcher reassigned PROTON-1884:

    Assignee: Andrew Stitcher  (was: Alan Conway)

> [c] example broker does not configure SASL correctly
> ----------------------------------------------------
>                 Key: PROTON-1884
>                 URL: https://issues.apache.org/jira/browse/PROTON-1884
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: python-binding
>    Affects Versions: proton-c-0.23.0
>            Reporter: Alan Conway
>            Assignee: Andrew Stitcher
>            Priority: Major
>             Fix For: proton-c-0.25.0
> The C example broker does not configure SASL correctly, it calls pn_sasl() before pn_transport_server()
which creates a client-side SASL config that does not respond to incoming SASL requests.
> Note: the original description of this issue described it as a python client problem
which is not the case. The python client has SASL on by default whereas other clients have
it off by default, so the python client showed the problem immediatley. Turning SASL on in
other clients showed the same problem.

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