Use SASL layer in AMQP 1.0 Erlang client #12029
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit ensures that AMQP 1.0 shovels will always use a SASL security layer when connecting to an AMQP 1.0 broker. Instead of skipping SASL, the client will use SASL mechanism ANONYMOUS.
#11999 mandates that AMQP 1.0 clients use a SASL security layer when connecting to a RabbitMQ 4.0 node.
This commit is only applied to the
v3.13.x
branch such that a shovel running on a 3.13.7 node will be able to connect via AMQP 1.0 to a RabbitMQ 4.x node.