Recent enhancements in RabbitMQ address the requirement for password and secret encryption across all major RabbitMQ plugins using rabbitmq.conf. Previously, several plugins required legacy configuration formats (using advanced.config) as described in this example, which many users found cumbersome.
These enhancements have expanded native encrypted value support to include password, private key, and secret fields for additional components including rabbitmq_management, rabbitmq_prometheus, and rabbitmq_web_stomp.
Supported Versions: The changes are backported across all active release lines. The initial release round including these changes consists of:
3.13.x (Up to 3.13.17)
4.1.x (Up to 4.1.13)
4.2.x (Up to 4.2.8)
4.3.x (Up to 4.3.2)
| Component / Plugin | Supported Configuration Keys for Encryption |
| Core RabbitMQ |
Partial templates (e.g., |
| Management |
|
| LDAP |
|
| Peer Discovery |
(SSL options passwords for Consul/Etcd via core partials) |
| Protocol & Other Plugins |
|
definitions.https.url: This key does not currently support encrypted values and represents the sole outstanding gap.
The fix will be available in future releases of RabbitMQ. Please subscribe to this article for the fix availability.