From 6793fde1ae2c28efccfdae14f61f40caf8f7dc4f Mon Sep 17 00:00:00 2001
From: Jocelyn Delalande <jdelalande@oasiswork.fr>
Date: Mon, 14 Sep 2015 20:50:21 +0200
Subject: [PATCH] Mentions BROKER_USE_SSL in security guide.

---
 docs/userguide/security.rst | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/userguide/security.rst b/docs/userguide/security.rst
index ef3cd96356f..4ccdb9d8c56 100644
--- a/docs/userguide/security.rst
+++ b/docs/userguide/security.rst
@@ -46,6 +46,9 @@ If your broker supports fine-grained access control, like RabbitMQ,
 this is something you should look at enabling. See for example
 http://www.rabbitmq.com/access-control.html.
 
+If supported by your broker backend, you can enable end-to-end SSL encryption
+and authentication using :setting:`BROKER_USE_SSL`.
+
 Client
 ------