You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Gordon Sim (Assigned) (JIRA)" <ji...@apache.org> on 2011/10/05 20:18:31 UTC
[jira] [Assigned] (QPID-3522) SASL EXTERNAL mechanism no longer
works
[ https://issues.apache.org/jira/browse/QPID-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gordon Sim reassigned QPID-3522:
--------------------------------
Assignee: Gordon Sim
> 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
> Assignee: 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:dev-subscribe@qpid.apache.org