#10 Add MQTT authentication #140
No reviewers
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K!140
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "#10-mqtt-login"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Implemmented MQTT authentication in the Mosquitto container
changes made:
disabled anonymous access
added password_file to mosquitto configuration
created a user automatically during container startup
updated mosquitto-init to use eclipse-mosquitto
Current credentails:
username: mqttuser, password: mqttpassword
Tested:
Mosquitto starts successfully with authentication enabled
Anonymous MQTT connections are rejected with NotAuthorized
Existing services fail until they are updated to provide credentials
Note:
Other services are not yet updated to use authentication. it will be handled in a separate task.
WIP: #10 Add MQTT authenticationto #10 Add MQTT authenticationassign me
All the changes for MQTT authentication look right, they do what they are supposed to do. I have noticed in relation to this change that all other MQTT clients that connect anonymously will most likely fail. I have checked both readTempSensorMockup and middleware and they will likely not work after the change as I cannot see any authentication. So both those files will have to be updated as well in another issue.
A question also: "chmod 0700 /mosquitto/config/passwd" should this be 0600 instead since this is a password file and doesn't need execute permissions?
A question: Now the credentials are hardcoded in the file. Is this a safe way or should they be stored in a safer space ( e.g environment variables)?
New pr was created.
Pull request closed