You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the files backend, if the ACL contains a user not listed in the password file, the plugin returns a fatal error and mosquitto shuts down:
`level=fatal msg="Backend register error: couldn't initialize files backend with error read acls: Files backend error: user user_not_in_acl
does not exist for acl at line 15."
This is different to 'standard' ACL/password behaviour for mosquitto, which silently ignores the ommission.
I would argue that this should not be a fatal error (by all means log a warning though) for the following reasons:
The admin may wish to temporarily disable a user by removing their password but not want to get rid of their ACL
For consistency and ease of comprehension, Files backend behaviour should mimic as closely as possible the standard Mosquitto implementation
The text was updated successfully, but these errors were encountered:
When using the files backend, if the ACL contains a user not listed in the password file, the plugin returns a fatal error and mosquitto shuts down:
This is different to 'standard' ACL/password behaviour for mosquitto, which silently ignores the ommission.
I would argue that this should not be a fatal error (by all means log a warning though) for the following reasons:
The text was updated successfully, but these errors were encountered: