You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Chuck Rolke (JIRA)" <ji...@apache.org> on 2015/10/15 19:43:05 UTC
[jira] [Commented] (DISPATCH-166) Use test-controlled SASL
configuration for system tests
[ https://issues.apache.org/jira/browse/DISPATCH-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14959278#comment-14959278 ]
Chuck Rolke commented on DISPATCH-166:
--------------------------------------
How to reproduce:
Tests PASS:
if there is no default SASL config file /etc/sasl2/qdrouterd.conf or if that file exists and has EXTERNAL in the mech_list:
{noformat}
mech_list: EXTERNAL ANONYMOUS DIGEST-MD5 PLAIN
{noformat}
Tests FAIL:
{noformat}
16: FAIL: test_ssl_cert_to_auth (system_tests_qdstat.QdstatSslTest)
16: FAIL: test_ssl_trustfile_cert_to_auth (system_tests_qdstat.QdstatSslTest)
{noformat}
if file /etc/sasl2/qdrouterd.conf exists and does not contain EXTERNAL in the mech_list:
{noformat}
mech_list: ANONYMOUS DIGEST-MD5 PLAIN
{noformat}
> Use test-controlled SASL configuration for system tests
> -------------------------------------------------------
>
> Key: DISPATCH-166
> URL: https://issues.apache.org/jira/browse/DISPATCH-166
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Tests
> Affects Versions: 0.5
> Reporter: Ted Ross
> Assignee: Chuck Rolke
> Fix For: 0.6
>
>
> Several of the SSL-related tests in the system-test suite can fail if the in-effect SASL configuration does not support the EXTERNAL mechanism. What is needed is for the test suite to create a proper configuration and use that for the routers under test.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org