[
https://issues.apache.org/jira/browse/QPID-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121317#comment-13121317
]
Gordon Sim commented on QPID-3522:
----------------------------------
The issue is indeed related to a distinction between null and a zero-length
string. In the cyrus sasl lib, when calling sasl_client_start, the response
returned is sometimes null (e.g. for CRAM-MD5) and sometimes a zero-length
string (e.g. for EXTERNAL). The corresponding call to sasl_server_start makes a
similar distinction. While AMQP 0-10 allows this distinction to be made on the
wire, the stubs and skeletons for the c++ client and broker don't distinguish
between the two cases.
> SASL EXTERNAL mechanism no longer works
> ---------------------------------------
>
> Key: QPID-3522
> URL: https://issues.apache.org/jira/browse/QPID-3522
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.13
> Reporter: Gordon Sim
> Priority: Blocker
> Fix For: 0.13
>
>
> Seems to be as a result of QPID-3393 (i.e. regression since 0.12) which was a
> fix for CRAM-MD5. From a simplistic point of view it seems like the CRAM-MD5
> mechanism requires an empty response string to be treated as null, whereas
> for the EXTERNAL mechanism an empty response should be treated as a zero
> length string. It may be though that there is more to this than that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
