Configuring secure replication links with TLS introduces challenges when encrypting private key passwords and utilizing client certificate authentication instead of standard username and password credentials.
Specifically, users need to:
Secure replication data in transit via TLS.
Encrypt private key passwords within the configuration files.
In rabbitmq.conf, encrypted values are supported only for a limited set of keys that were explicitly implemented for tagged encrypted values.
Replication-specific TLS password keys are not generally documented as part of that supported rabbitmq.conf encrypted-value set, so they may need to be configured in advanced.config instead.
Following links can be useful: