Is your feature request related to a problem? Please describe.

thin-edge.io. components only support connecting to a local MQTT broker that either has no authentication, or cert based client authentication.

In scenarios where users are using an already configured local MQTT broker and it is fairly common that username/password authentication is used (as username/password requires less setup/Maintenance then cert based authentication).

Allow users to connect thin-edge.io components to a local MQTT broker which is using a username/password.

Describe the solution you'd like

Allow users to connect thin-edge.io components to a local MQTT broker which is using a username/password.

For example, the following are the suggested configuration value to allow users to configure using username/password based authentication when connecting to the local MQTT broker.

tedge config set mqtt.client.auth.username "<username>"
tedge config set mqtt.client.auth.password_file "<file_path>"

The above values should also be able to read from the env variables

• TEDGE_MQTT_CLIENT_AUTH_USERNAME
• TEDGE_MQTT_CLIENT_AUTH_PASSWORD_FILE

Where the password_file points to a file containing the password on the first line.

Describe alternatives you've considered

Additional context