Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add rabbitmq_ssl parameter to enable SSL transport to RabbitMQ #249

Merged
merged 3 commits into from
Sep 23, 2014
Merged

Add rabbitmq_ssl parameter to enable SSL transport to RabbitMQ #249

merged 3 commits into from
Sep 23, 2014

Conversation

misterdorm
Copy link
Contributor

This new parameter enables SSL transport when connecting to RabbitMQ. This way
you can use SSL to connect to RabbitMQ without configuring it for certificate
authentication (rabbitmq_ssl_private_key and rabbitmq_ssl_cert_chain parameters.)

If you have rabbitmq_ssl => true with no other rabbitmq_ssl parameters, the
rabbitmq.json config file will have an empty ssl { } stanza in it. This makes
Sensu use SSL transport when connecting to RabbitMQ, but it will not attempt
certification authentication.

Mike Dorman added 3 commits September 22, 2014 13:53
This new parameter enables SSL transport when connecting to RabbitMQ.  This way
you can use SSL to connect to RabbitMQ without configuring it for certificate
authentication (rabbitmq_ssl_private_key and rabbitmq_ssl_cert_chain parameters.)

If you have rabbitmq_ssl => true with no other rabbitmq_ssl parameters, the
rabbitmq.json config file will have an empty ssl { } stanza in it.  This makes
Sensu use SSL transport when connecting to RabbitMQ, but it will not attempt
certification authentication.
jamtur01 added a commit that referenced this pull request Sep 23, 2014
Add rabbitmq_ssl parameter to enable SSL transport to RabbitMQ
@jamtur01 jamtur01 merged commit c8e9295 into sensu:master Sep 23, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants