#auth_pluginĪuth_plugin /home/USER/mosquitto/auth-plug.soĪuth_opt_http_port 80 #auth_opt_http_hostname example. # Specify the path to the loadable plugin and see the # "Authentication and topic access plugin options" section below. The auth_plugin # allows another authentication method to be used. The default support is described in "Default # authentication and topic access control" below. #allow_anonymous true # In addition to the clientid_prefixes, allow_anonymous and TLS # authentication options, username based authentication is also # possible. The plugin builds on top of RabbitMQ core protocol's entities: exchanges and queues. It also makes it possible for MQTT clients to interoperate with AMQP 0-9-1, AMQP 1.0, and STOMP clients. If set to # false then a password file should be created (see the # password_file option) to control authenticated client access. RabbitMQ MQTT plugin targets MQTT 3.1.1 and supports a broad range of MQTT clients. #clientid_prefixes # Boolean value that determines whether clients that connect # without providing a username are allowed to connect. # For example, setting "secure-" here would mean a client "secure- # client" could connect but another with clientid "mqtt" couldn't. # = # Security # = # If set, only clients that have a matching prefix on their # clientid will be allowed to connect to the broker.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |