Why DIGEST-MD5 or CRAM-MD5 authentication mechanism does not work in qpid broker?

Solution Verified - Updated -

Issue

We are failing to authenticate our application using DIGEST-MD5 authentication method. While PLAIN method works properly.

We tried that in more qpid clients (Java/JMS, C++, Python), everytime with the same result.

As both SASL methods use the same credentials stored in the same file (and differ in the authentication method only), we are curious why DIGEST-MD5 does not work.

The same problems we spotted when using CRAM-MD5 mechanism that does not work either.

Environment

  • MRG Messaging (any version)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content