This description is outdated, see the post by @cicoub13 for an alternative implementation.
Description
Would it be possible via the config to disable Gladys built-in auth? I would like to do that and then put basic auth in front of it via my reverse proxy (Caddy). It’s not that I don’t trust Gladys auth implementation, but I do trust the one from the reverse proxy more.
Hello,
Today it’s not possible, and we don’t plan to make it deactivatable as is. Gladys authentication isn’t just for « locking the door »: it’s mainly used to know which user is performing the action. Every request and every real-time connection (WebSocket) is linked to a user. Their role (admin / resident), their dashboards, their language, their messages, scene notifications, etc., all depend on it. Disabling it would be like giving full admin access to anyone who can reach Gladys’s port.
To go further, the approach that would make sense on Gladys’s side would be delegated authentication to the proxy: Gladys would trust a header like Remote-User, but only if it comes from a declared proxy IP, and would associate it with an existing Gladys user. We’d keep the notion of user and role while letting Caddy / Authelia handle the login. If you’re interested, don’t hesitate to turn this request into a feature request to see if there’s demand!
Yes that would make sense to me. Thanks for thinking about this. I’ve updated the post title.