qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Ross <jr...@redhat.com>
Subject Connecting to the router
Date Tue, 13 Sep 2016 23:33:00 GMT
Some potentially interesting things.

## Components

python-qpid-proton-0.13.1-1.fc24.x86_64
python-qpid-messaging-0.34-9.fc24.x86_64 (qpid*_*messaging)
qpid-dispatch-router-0.6.1-2.fc24.x86_64

## Listener config

listener {
    host: 0.0.0.0
    port: amqp
    authenticatePeer: on
    saslMechanisms: ANONYMOUS
}

## host: 0.0.0.0 allows connection via localhost from qpid_messaging but
not from proton

My qpid_messaging client can connect, using localhost in its connection
info, but my proton client cannot (connection refused). Using '::' instead
of '0.0.0.0' allows either to connect.  Perhaps the way proton resolves
localhost is different.

## "authenticatePeer: on" strips ANONYMOUS

This was a surprise to me.  I had explicitly enabled ANONYMOUS.  And I
confess I was mentally reading 'authenticatePeer' to mean enable SASL.
Which component is stripping it, proton or dispatch or cyrus?  Should it be
stripped when I positively express a desire for it?  If we keep this
behavior, we should add a note about it to the qdrouterd.conf man page.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message