[
https://issues.apache.org/jira/browse/QPID-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13857053#comment-13857053
]
Ulrich Romahn commented on QPID-5438:
-------------------------------------
After debugging the issue, here are some more details:
I used "saslpasswd2 -f /var/lib/qpidd/qpidd.sasldb -u QPID guest" with a
password 'guest' to create a user.
I started qpidd with:
qpidd -d --auth yes --realm QPID --log-enable trace+:Protocol --log-enable
debug+:Security --log-enable info+ --sasl-config /usr/local/etc/sasl2/
--acl-file qpidd.acl
I used the latest AMQP 1-0 JMS Client library (trunk) to connect to the qpidd
broker with the following URL:
amqp://guest:guest@<my-IP-Address>:5672
I then started my client application and got the following output in the log
file:
2013-12-26 20:23:48 [Network] info Set TCP_NODELAY on connection to
XX.XX.XX.XX:37512
2013-12-26 20:23:48 [Broker] info Using AMQP 1.0 (with SASL layer)
2013-12-26 20:23:48 [Security] debug External ssf=0 and auth=
2013-12-26 20:23:48 [Security] debug min_ssf: 0, max_ssf: 256, external_ssf: 0
2013-12-26 20:23:48 [Security] info SASL: Mechanism list: ANONYMOUS
2013-12-26 20:23:48 [Protocol] debug qpid.YY.YY.YY.YY:5672-XX.XX.XX.XX:37512
Sent SASL-MECHANISMS(ANONYMOUS) 31
2013-12-26 20:23:48 [Protocol] debug qpid.YY.YY.YY.YY:5672-XX.XX.XX.XX:37512
writing protocol header: 1-0
2013-12-26 20:23:48 [Protocol] debug qpid.YY.YY.YY.YY:5672-XX.XX.XX.XX:37512
Received SASL-INIT(ANONYMOUS, )
2013-12-26 20:23:48 [Security] info SASL: Starting authentication with
mechanism: ANONYMOUS
2013-12-26 20:23:48 [Protocol] debug qpid.YY.YY.YY.YY:5672-XX.XX.XX.XX:37512
Sent SASL-CHALLENGE() 22
2013-12-26 20:23:48 [Security] info qpid.YY.YY.YY.YY:5672-XX.XX.XX.XX:37512
Challenge issued
2013-12-26 20:23:58 [System] error Connection
qpid.YY.YY.YY.YY:5672-XX.XX.XX.XX:37512 No protocol received closing
2013-12-26 20:23:58 [Security] info qpid.YY.YY.YY.YY:5672-XX.XX.XX.XX:37512
Connection closed prior to authentication completing
2013-12-26 20:23:58 [Security] info qpid.YY.YY.YY.YY:5672-XX.XX.XX.XX:37512
Connection closed prior to authentication completing
Here is the content of my qpidd.conf in the sasl-config file:
pwcheck_method: auxprop
auxprop_plugin: sasldb
sasldb_path: /var/lib/qpidd/qpidd.sasldb
mech_list: PLAIN ANONYMOUS DIGEST-MD5 EXTERNAL
Not sure if this is a bug in the Java client or the actual CPP broker.
> [AMQP 1.0 JMS client] Connecting to qpid-cpp with SASL2 hangs
> -------------------------------------------------------------
>
> Key: QPID-5438
> URL: https://issues.apache.org/jira/browse/QPID-5438
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.27
> Environment: qpid-cpp 0.27 (from trunk),
> qpid-amqp-1-0-client-jms-0.28-SNAPSHOT (from trunk). Broker running on CentOS
> 6..0, client running on Linuxmint 15
> Reporter: Ulrich Romahn
> Priority: Blocker
>
> I have SASL2 enabled on the broker with the correct configuration.
> When connecting to the broker from the Java client using the following URL
> amqp://guest:guest@qpid-cpp-server:5672 I am getting an error message on the
> broker, saying that no protocol was sent and it will close the connection.
> This will cause the client to hang while trying to connect.
> I suspect the client will eventually get a timeout exception, but I never
> waited that long. The same connection succeeds on the Java Broker v 0.24.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
