RabbitMQ: BrokerUnreachableException when setting UseExternalAuthMechanism=false

[danielmarbach]

Symptoms

ServiceControl fails to connect to RabbitMQ and throws a BrokerUnreachableException when starting up or attempting to communicate with the broker.

Who's affected

You are affected if:

• You are using ServiceControl version 6.14.
• You are using RabbitMQ as the transport.
• Your RabbitMQ connection string includes UseExternalAuthMechanism=false.

Root cause

This is a regression that was introduced by #5383.

During the changes, we did not consider that the pure existence of the key could lead to the external authentication mechanism being set.

Confirmed workarounds

Remove UseExternalAuthMechanism=false from the connection string

Original bug report

Describe the bug

Description

This is a regression that was introduced by #5383.

During the changes, we did not consider that the pure existence of the key could lead to the external authentication mechanism being set.

Expected behavior

UseExternalAuthMechanism=false should not lead to BrokerUnreachableExceptions

Actual behavior

UseExternalAuthMechanism=false leads to BrokerUnreachableException

Versions

Please list the version of the relevant packages or applications in which the bug exists.

Affects 6.14 only, which contains the transport upgrade

Steps to reproduce

UseExternalAuthMechanism=false in the connection string

Relevant log output

Additional Information

Workarounds

Remove UseExternalAuthMechanism=false from the connection string

Possible solutions

Additional information