On 19/06/18 17:56, Alan Conway wrote:
On Tue, Jun 19, 2018 at 11:55 AM, Gordon Sim <g...@redhat.com> wrote:
On 19/06/18 16:44, Alan Conway wrote:
A related (not identical) issue is
https://issues.apache.org/jira/browse/DISPATCH-244
Andrews fix will fix that problem as well as the failures discussed here.
Would setting the sasl configuration of the router for the tests not help?
Yes, I believe most of them have been set by now.
Installing config files will not, nor will it help with developers trying
out examples in a source build etc.
True, though you could fix that by having the examples set the sasl
mechanisms explicitly.
True again, but I would prefer to avoid mysterious failures by default,
I would argue that a better way to do that is to be explicit about how
servers are configured. After all what if some other mechanism plugin
turns out to have unanticipated side effects.
rather than via extra code/configuration that .developers must remember,
I think a sasl server *should* be configured, and I think the failure to
do so is what actually causes the problems.
even if we do modify every example to use mechs=ANONYMOUS. The fact that
*we* didn't know we needed to use ANONYMOUS in all tests and examples until
the problem bit us makes me worry that others will fall down the same
rabbit-hole.
Again, I think a better solution there would be either to modify the
server examples to explicitly set the mechanisms or to improve the
documentation to explain the need to configure sasl better (as I say,
the python examples README does this, but we could find ways to
emphasise it if it is indeed tripping lots of people up).
To me the problem is one of server misconfiguration and it would be
better to try and tackle that directly rather than impose a change that
mysteriously eliminates server offered mechanisms on all users.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
