shovel: Support SASL EXTERNAL and/or SASL disabled #14775
Replies: 1 comment 2 replies
-
|
@carlsmedstad your conclusion is incorrect. Shovels use regular AMQP 0-9-1 and AMQP 1.0 clients, so anything that is supported for those clients is supported by shovels. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe.
We're trying to instantiate a Dynamic Shovel propagating messages from a third-party AMQP 1.0 broker to a queue in our cluster (deployed using cluster-operator). The ambition is to replace a Python component built with python-qpid-proton.
We're creating the shovel using the API:
The shovel fails to connect to the third-party broker due to failed SASL authentication:
We have confirmed that our old Python component can connect to the broker using both:
However, we're unable to configure the shovel to do either of the above:
sasl=noneis provided to the shovel (in the URI). So it seems it's not possible to disable SASL authentication.amqp10_client_connectionmodule seems to support SASL EXTERNAL, theparse_urifunction inamqp10_client.erldoes not. Hence, it seems like SASL EXTERNAL is currently not supported in the shovel plugin.Appreciate any input on how to resolve this, thanks!
Describe the solution you'd like
The shovel plugin supports:
Describe alternatives you've considered
No response
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions