[
https://issues.apache.org/jira/browse/PROTON-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16540443#comment-16540443
]
ASF subversion and git services commented on PROTON-1884:
---------------------------------------------------------
Commit adefd01f394b33be056dc822c60439ef5d775c6c in qpid-proton's branch
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=adefd01 ]
PROTON-1884: [c] example broker does not configure SASL correctly
To configure server-side SASL the application must call
pn_transport_set_server() before pn_sasl(). The pn_proactor_accept2() function
calls set_server automatically but it is too late for SASL config.
Fixed example broker and clarified the API docs.
> [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]
