Bug 1130575 - Java client does not support digest-md5 sasl authentication mechanism
Summary: Java client does not support digest-md5 sasl authentication mechanism
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-java
Version: 2.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: Messaging QE
URL:
Whiteboard:
Depends On: 1130474
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-15 14:58 UTC by Michal Toth
Modified: 2019-02-08 14:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1130474
Environment:
Last Closed:


Attachments (Terms of Use)

Description Michal Toth 2014-08-15 14:58:03 UTC
+++ This bug was initially created as a clone of Bug #1130474 +++

Description of problem:
Any connection using using digest-md5 sasl mechanism between broker and java clients results in ConnectionException.


Version-Release number of selected component (if applicable):
qpid-java-common-0.18-8.el6_4.noarch
qpid-java-client-0.18-8.el6_4.noarch
qpid-java-example-0.18-8.el6_4.noarch

How reproducible:
100%

Steps to Reproduce:
Send a message to broker using digest-md5 authentication mechanism.

Actual results:
Exception is thrown and connection refused.

Expected results:
Client should successfully send a message to broker using DIGEST-MD5 sasl mechanism.

Additional info:
./run_example.sh org.apache.qpid.example.Spout --broker=guest:guest@192.168.122.146:5672 --broker-option=sasl_mechs=DIGEST-MD5  --count 1 test_q

{broker-option=sasl_mechs=DIGEST-MD5, count=1, broker=guest:guest@192.168.122.146:5672}
Exception in thread "main" org.apache.qpid.AMQConnectionFailureException: Client and broker have no SASL mechanisms in common. Broker allows : DIGEST-MD5 PLAIN ANONYMOUS Client has : [EXTERNAL, GSSAPI, CRAM-MD5-HASHED, CRAM-MD5, AMQPLAIN, PLAIN, ANONYMOUS] Client restricted itself to : DIGEST-MD5 [error code 200: reply success]
	at org.apache.qpid.client.AMQConnection.<init>(AMQConnection.java:460)
	at org.apache.qpid.client.AMQConnection.<init>(AMQConnection.java:219)
	at org.apache.qpid.example.OptionParser.createConnection(OptionParser.java:283)
	at org.apache.qpid.example.Spout.<init>(Spout.java:87)
	at org.apache.qpid.example.Spout.main(Spout.java:147)
Caused by: org.apache.qpid.AMQException: Cannot connect to broker: Client and broker have no SASL mechanisms in common. Broker allows : DIGEST-MD5 PLAIN ANONYMOUS Client has : [EXTERNAL, GSSAPI, CRAM-MD5-HASHED, CRAM-MD5, AMQPLAIN, PLAIN, ANONYMOUS] Client restricted itself to : DIGEST-MD5 [error code 200: reply success]
	at org.apache.qpid.client.AMQConnectionDelegate_0_10.makeBrokerConnection(AMQConnectionDelegate_0_10.java:239)
	at org.apache.qpid.client.AMQConnection.makeBrokerConnection(AMQConnection.java:604)
	at org.apache.qpid.client.AMQConnection.<init>(AMQConnection.java:383)
	... 4 more
Caused by: org.apache.qpid.transport.ConnectionException: Client and broker have no SASL mechanisms in common. Broker allows : DIGEST-MD5 PLAIN ANONYMOUS Client has : [EXTERNAL, GSSAPI, CRAM-MD5-HASHED, CRAM-MD5, AMQPLAIN, PLAIN, ANONYMOUS] Client restricted itself to : DIGEST-MD5
	at org.apache.qpid.transport.ConnectionException.rethrow(ConnectionException.java:67)
	at org.apache.qpid.transport.Connection.connect(Connection.java:269)
	at org.apache.qpid.client.AMQConnectionDelegate_0_10.makeBrokerConnection(AMQConnectionDelegate_0_10.java:219)
	... 6 more
Caused by: org.apache.qpid.transport.ConnectionException: Client and broker have no SASL mechanisms in common. Broker allows : DIGEST-MD5 PLAIN ANONYMOUS Client has : [EXTERNAL, GSSAPI, CRAM-MD5-HASHED, CRAM-MD5, AMQPLAIN, PLAIN, ANONYMOUS] Client restricted itself to : DIGEST-MD5
	at org.apache.qpid.client.transport.ClientConnectionDelegate.createSaslClient(ClientConnectionDelegate.java:92)
	at org.apache.qpid.transport.ClientDelegate.connectionStart(ClientDelegate.java:92)
	at org.apache.qpid.transport.ClientDelegate.connectionStart(ClientDelegate.java:43)
	at org.apache.qpid.transport.ConnectionStart.dispatch(ConnectionStart.java:95)
	at org.apache.qpid.transport.ConnectionDelegate.control(ConnectionDelegate.java:49)
	at org.apache.qpid.transport.ConnectionDelegate.control(ConnectionDelegate.java:40)
	at org.apache.qpid.transport.Method.delegate(Method.java:163)
	at org.apache.qpid.transport.Connection.received(Connection.java:391)
	at org.apache.qpid.transport.Connection.received(Connection.java:67)
	at org.apache.qpid.transport.network.Assembler.emit(Assembler.java:97)
	at org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:183)
	at org.apache.qpid.transport.network.Assembler.frame(Assembler.java:131)
	at org.apache.qpid.transport.network.Frame.delegate(Frame.java:128)
	at org.apache.qpid.transport.network.Assembler.received(Assembler.java:102)
	at org.apache.qpid.transport.network.Assembler.received(Assembler.java:44)
	at org.apache.qpid.transport.network.InputHandler.next(InputHandler.java:189)
	at org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:105)
	at org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:44)
	at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:152)
	at java.lang.Thread.run(Thread.java:745)


Note You need to log in before you can comment on or make changes to this bug.