[
https://issues.apache.org/jira/browse/QPID-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642489#action_12642489
]
Martin Ritchie commented on QPID-1182:
--------------------------------------
The reason for the strange test failures could be due to two issues.
1) QPID-1394, the client and broker compete to register their respective SASL
plugins however the broker should always win but if the broker fails to
register then non of the Qpid SASL plugins will be available and authentication
cannot take place. This is probably the most likely cause of the sasl errors
Qpid-1394 ensures that the client and broker do not compete to register using
the same name for their sasl providers.
2) QPID-1390 could mean that the wrong SASL plugin is being used for
authentication as the broker does not remove the custom SASL providers on
shutdown. This update ensures that on shutdown they are removed so should
prevent any further problems.
> SimpleACLTest authentication failures
> -------------------------------------
>
> Key: QPID-1182
> URL: https://issues.apache.org/jira/browse/QPID-1182
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: M4
>
> Attachments:
> TEST-org.apache.qpid.server.security.acl.SimpleACLTest.txt
>
>
> Summary:
> The only test failure I am now seeing occurs in the SImpleACLTest I have seen
> a number of failures in both of these test cases:
> testClientPublishUsingTransactionSuccess
> testServerPublishUsingTransactionSuccess
> In both situtations the problem has been 'authentication failed' error code
> 530.
> The additional logging shows that the exception was that CRAM-MD5
> authentication failed:
> pool-6-thread-2 2008-07-17 16:49:54,652 INFO
> [qpid.server.handler.ConnectionSecureOkMethodHandler] Authentication
> failed:CRAM-MD5 authentication failed
> Attached is one full log output showing the failure.
> The error occurs before any ACL code is touched so I'm not sure why it is
> only in this test that we are seeing the failures.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
