[
https://issues.apache.org/jira/browse/PROTON-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Threlfall updated PROTON-2064:
-----------------------------------
Priority: Critical (was: Major)
Description:
When using the electron version of the go binding with a qpid-cpp 1.39 broker,
Digest-MD5 connections seem to be rejected by the broker despite the correct
credentials. When using CRAM-MD5 there is no issue with the same credentials.
The python version connects happily with DIGEST-MD5. The error on the golang
client side
Error: amqp:connection:framing-error: connection aborted
On the broker it reads:
2019-06-06 10:14:43 [Broker] info Using AMQP 1.0 (with SASL layer)
2019-06-06 10:14:43 [Security] info SASL: Mechanism list: DIGEST-MD5 PLAIN
CRAM-MD5
2019-06-06 10:14:45 [Security] info qpid.[::1]:5672-[::1]:46190 Connection
closed prior to authentication completing
are there any special cases with digest-md5 I could be missing for the golang
binding?
was:
When using the electron version of the go binding with a qpid-cpp 1.39 broker,
Digest-MD5 connections seem to be rejected by the broker despite the correct
credentials. When using CRAM-MD5 there is no issue with the same credentials.
The python version connects happily with DIGEST-MD5. The error on the golang
client side reads.
{code:java}
Error: amqp:connection:framing-error: connection aborted
{code}
> Go Digest MD5 connection issues
> -------------------------------
>
> Key: PROTON-2064
> URL: https://issues.apache.org/jira/browse/PROTON-2064
> Project: Qpid Proton
> Issue Type: Bug
> Components: go-binding
> Affects Versions: proton-c-0.27.0, proton-c-0.28.0
> Reporter: Matt Threlfall
> Assignee: Alan Conway
> Priority: Critical
>
> When using the electron version of the go binding with a qpid-cpp 1.39
> broker, Digest-MD5 connections seem to be rejected by the broker despite the
> correct credentials. When using CRAM-MD5 there is no issue with the same
> credentials. The python version connects happily with DIGEST-MD5. The error
> on the golang client side
> Error: amqp:connection:framing-error: connection aborted
> On the broker it reads:
> 2019-06-06 10:14:43 [Broker] info Using AMQP 1.0 (with SASL layer)
> 2019-06-06 10:14:43 [Security] info SASL: Mechanism list: DIGEST-MD5 PLAIN
> CRAM-MD5
> 2019-06-06 10:14:45 [Security] info qpid.[::1]:5672-[::1]:46190 Connection
> closed prior to authentication completing
>
> are there any special cases with digest-md5 I could be missing for the golang
> binding?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
