Update set allow_anonymous flag to be explicitly true

In newer mosquitto version the default for the allow_anonymous config
flag was changed from true to a conditional true. It defaults to false
if you have certain auth methods enabled. Since the config generated by
puppet-mosquitto has these auth methods enabled the implicit value of
true changed to false when we upgraded the mosquitto version. This
commit fixes this case by explicitly setting allow_anonymous to be true
so that we allow anonymous connections so we can have the public
read only access to the firehose.

Change-Id: I6fceb1daf55b0e3a7345461dca1c4c7ef5a80440
This commit is contained in:
Matthew Treinish 2020-09-09 09:45:38 -04:00
parent 0c6ea529f8
commit e05b5f283d
No known key found for this signature in database
GPG Key ID: FD12A0F214C9E177
1 changed files with 13 additions and 5 deletions

View File

@ -537,11 +537,19 @@ log_timestamp true
#clientid_prefixes
# Boolean value that determines whether clients that connect
# without providing a username are allowed to connect. If set to
# false then a password file should be created (see the
# password_file option) to control authenticated client access.
# Defaults to true.
#allow_anonymous true
# without providing a username are allowed to connect.
# If set to false then another means of connection should be created to
# control authenticated client access.
#
#Defaults to true if no other security options are set. If password_file or
#psk_file is set, or if an authentication plugin is loaded which implements
#username/password or TLS-PSK checks, then allow_anonymous defaults to false.
#
#If per_listener_settings is true, this option applies to the current listener
#being configured only. If per_listener_settings is false, this option applies
#to all listeners.
#
allow_anonymous true
# In addition to the clientid_prefixes, allow_anonymous and TLS
# authentication options, username based authentication is also