[
https://issues.apache.org/jira/browse/PROTON-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher reopened PROTON-1884:
-------------------------------------
I think this is the wrong solution.
You shouldn't need to call pn_transport_set_server() before pn_sasl(). Rather
when you call pn_transport_ser_server() as long as you are not connected yet it
should update any existing transport->sasl member.
There is no need to enforce the somewhat error-prone and unintuitive ordering.
> [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: Alan Conway
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
