More in-depth ACL
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mosquitto |
New
|
Wishlist
|
Unassigned | ||
Bug Description
It'd be nice to be able to have a more in-depth ACL implementation.
Possibly not as advanced as squid's, http://
I'd like to be able to set the conditions where a client prefix/login is required - for example all public IP addresses, not local addresses, or not the loopback address. Maybe even different mount points for clients connecting from different IPs/with different usernames/different client prefixes.
I'd imagine the best implementation of this would be by having the authorization and the current listener and mount_point configuration directives as a subset of the ACLs, ie, read/write access and the mount point a client is connected to being based upon the ACLs - that clients fall into via a set of conditions - authorized user AND/OR correct prefix AND/OR correct IP range.
| Changed in mosquitto: | |
| importance: | Undecided → Wishlist |
| Roger Light (roger.light) wrote | #1 |
Hi there,
I'm migrating bugs to Eclipse. The new url for this bug is:
https:/