[
https://issues.apache.org/jira/browse/DISPATCH-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14951129#comment-14951129
]
Chuck Rolke commented on DISPATCH-172:
--------------------------------------
Commit 4226b9 cleans up the config passed down the router but it doesn't make
any difference in the test behavior. The test is using SASL EXTERNAL either
way. Putting debug statements inside config.py configure_dispatch:config shows:
{noformat}
Test spec:
'sasl-mechanisms:': 'EXTERNAL'
Config file listener section:
'sasl-mechanisms': 'ANONYMOUS'
'sasl-mechanisms:': 'EXTERNAL'
Inside the router config processing:
'sasl-mechanism': ': EXTERNAL'
{noformat}
>From the list of mechanisms ': EXTERNAL' the code used EXTERNAL and the test
>worked as expected.
> QDStat system test never tests SASL EXTERNAL
> --------------------------------------------
>
> Key: DISPATCH-172
> URL: https://issues.apache.org/jira/browse/DISPATCH-172
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
> Affects Versions: 0.5
> Reporter: Chuck Rolke
> Assignee: Chuck Rolke
> Fix For: 0.6
>
>
> Test config tries to specify EXTERNAL mechanism but never overwrites default
> ANONYMOUS.
> {noformat}
> listener {
> addr: 0.0.0.0
> requireSsl: yes
> saslMechanisms: ANONYMOUS
> ssl-profile: server-ssl
> authenticatePeer: yes
> saslMechanisms:: EXTERNAL
> port: 29067
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
