Shovel over SSL Configuration #319
-
Hi Team, Thank you, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
The cert file and key file are needed for mTLS. You don't need to configure them in this case. uri specification can be found here: https://www.rabbitmq.com/uri-query-parameters.html#basics The configuration depends on your own set up. Shovel acts as a client APP for both the source and destination RabbitMQ. Depends on how you've signed your server certs and where you are configuring shovel, you might not need to specify path to the ca cert file. For example, if you are 1) not using mTLS 2) both your dest&src RabbitMQ are set up to trust the same CA 3) you are configuring shovel in either the source or the destination RabbitMQ, you don't need to configure the ca cert in your URI because it should already be trusted. On the other hand, you are configuring Shovel in a third RabbitMQ cluster, not source or destination, and that third RabbitMQ does not trust the source and destination RabbitMQ's CAs, you will need to provide path to CA certs in both the destination and source URI. |
Beta Was this translation helpful? Give feedback.
The cert file and key file are needed for mTLS. You don't need to configure them in this case.
uri specification can be found here: https://www.rabbitmq.com/uri-query-parameters.html#basics
The configuration depends on your own set up. Shovel acts as a client APP for both the source and destination RabbitMQ. Depends on how you've signed your server certs and where you are configuring shovel, you might not need to specify path to the ca cert file.
For example, if you are 1) not using mTLS 2) both your dest&src RabbitMQ are set up to trust the same CA 3) you are configuring shovel in either the source or the destination RabbitMQ, you don't need to configure the ca cert in your URI because i…