AuthenticationThe authentication options described below allow a wide range of
possibilities in conjunction with the listener options. This
- section aims to clarify the possibilities.
+ section aims to clarify the possibilities. An overview is also available at
+ The simplest option is to have no authentication at all. This is
the default if no other options are given. Unauthenticated
encrypted support is provided by using the certificate based
@@ -54,6 +55,11 @@
vulnerable to interception. Use the
to control whether passwords
are required globally or on a per-listener basis.
+ Mosquitto provides the Dynamic Security plugin which handles
+ username/password authentication and access control in a much
+ more flexible way than a password file. See
+
+ When using certificate based encryption there are three options
that affect authentication. The first is require_certificate, which
may be set to true or false. If false, the SSL/TLS component of the
@@ -164,6 +170,9 @@
Reloaded on reload signal. The currently loaded ACLs
will be freed and reloaded. Existing subscriptions will
be affected after the reload.
+ See also
+
+
@@ -267,6 +276,9 @@
alongsize , the plugin
checks will run after the built in checks.Not currently reloaded on reload signal.
+ See also
+
+
@@ -753,7 +765,9 @@ log_timestamp_format %Y-%m-%dT%H:%M:%S
Clients that are already connected will not be
affected.
See also
- mosquitto_passwd1.
+ mosquitto_passwd1 and
+
+