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
Would be great to be able to per specified custom location set access list controls.
Right now you will have to manually recreate access lists when for example wanting to limiting access to a specific path. I found you can reuse the user access lists (like so: auth_basic_user_file /data/access/1;) but you'll have to look which access file belongs to which users and if you (as myself) combine multiple rules in an access list (ip whitelisting combined with basic auth) then you are out of luck and will have to manually rewrite these rules in the advanced config box.
Besides this, right now if I want to only allow free access to a subpath (for example home-assistant.example.com/api) but want to restricts access to all other paths (home-assistant.example.com/) you will have to configure a "Public" proxy and then create restriction rules on all these other paths to make this possible which feels the wrong way around; it would be nice to be able to restrict the proxy as a whole and simply "whitelist" specific custom locations.
Would this be possible and if so hard to implement from an architectural stand point? Would be interested to contribute if there's more interest in a feature like this.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Would be great to be able to per specified custom location set access list controls.
Right now you will have to manually recreate access lists when for example wanting to limiting access to a specific path. I found you can reuse the user access lists (like so: auth_basic_user_file /data/access/1;) but you'll have to look which access file belongs to which users and if you (as myself) combine multiple rules in an access list (ip whitelisting combined with basic auth) then you are out of luck and will have to manually rewrite these rules in the advanced config box.
Besides this, right now if I want to only allow free access to a subpath (for example home-assistant.example.com/api) but want to restricts access to all other paths (home-assistant.example.com/) you will have to configure a "Public" proxy and then create restriction rules on all these other paths to make this possible which feels the wrong way around; it would be nice to be able to restrict the proxy as a whole and simply "whitelist" specific custom locations.
Would this be possible and if so hard to implement from an architectural stand point? Would be interested to contribute if there's more interest in a feature like this.
Beta Was this translation helpful? Give feedback.
All reactions